

Get Users Current Time / Date
Core Utility
Available ActionsEach successful request consumes credits as outlined below.
get_current_datetime3cr
Details
Agents running in the cloud don't know what timezone their users are in. This tool returns the current date and time in the user's configured timezone so agents can schedule, format, and reason about time using the user's local context. The tool returns both local and UTC timestamps, the timezone name, and useful derived fields such as local date, local time, and UTC offset. This enables time aware workflows like reminders, deadlines, and calendar or messaging logic without repeatedly asking the user what time zone they are in.
Workflows Using This Tool
2 / 7- Narrated Walkthrough to a Numbered SOP Document
- One Plaud Recording, Several Differently Formatted Summaries
- Plaud Transcripts Corrected With Your Own Terminology Glossary
- Plaud Recordings to Google Calendar Events
- Plaud Spoken Field Notes to a Structured Sheet
- Plaud Spoken Commitments to Telegram Reminders
- Appointment Scheduling and Route Planner
Workflow
Saves ~20 min
Gets you past the one-template-per-recording ceiling. The Plaud app applies a single AutoFlow template to a recording, so if you want a short recap for yourself, a decisions-only version for the people who missed it, and a clean action list for your task manager, you are re-running or rewriting by hand. This workflow reads the transcript once and produces every format you have defined in a single pass: you list the output formats you want in a Google Sheet, each with a name and a description of the shape and audience, and the workflow generates all of them from the same source text and writes them into one Google Doc per recording with a section for each. Because every version comes from the same read of the transcript, they stay consistent with each other rather than drifting the way separately generated summaries do. Formats are yours to change at any time by editing the sheet, with no re-recording and no template juggling in the app. A processed log keeps each recording to a single pass so it can run on a schedule over everything new.
Use Cases
Get current local time for a user, Build time aware reminders, Schedule messages in the user timezone, Add local timestamps to logs, Convert between UTC and user local time, Validate timezone configuration, Generate date strings for reports
Dynamic MCP Setup
Connect once through AgentPMT Dynamic MCP, then use approved tools from the same agent connection.
30 Second Setup
STDIO connector for Claude Code, Codex, Cursor, Zed, and other LLMs that require STDIO or custom connections.
npm install -g @agentpmt/mcp-routeragentpmt-setupHosted Streamable HTTPS
MCP endpoint for browser-based apps like ChatGPT, Claude, Grok, or any time you want a streamable connection with no local install.
https://api.agentpmt.com/mcpConfig Example
Use the hosted endpoint directly in clients that support remote MCP. Store your Bearer token in the client config or secret field.
{
"mcpServers": {
"agentpmt": {
"type": "streamable-http",
"url": "https://api.agentpmt.com/mcp",
"headers": {
"Authorization": "Bearer <AGENTPMT_BEARER_TOKEN>",
"x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}"
}
}
}
}Need client videos, organization controls, audit details, and the full feature overview?
More About Dynamic MCPFrequently Asked Questions
How do I connect this tool to an external agent?
You can install the local MCP server by opening a terminal and running:
Install commands
npm install -g @agentpmt/mcp-router
agentpmt-setupThis will connect you to local agents like Claude Code, Windsurf, Grok Build, Cursor, etc.
Alternatively you can connect to the hosted version with this config block, no installation required:
Hosted MCP config
{
"mcpServers": {
"agentpmt": {
"type": "streamable-http",
"url": "https://api.agentpmt.com/mcp",
"headers": {
"Authorization": "Bearer <AGENTPMT_BEARER_TOKEN>",
"x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}"
}
}
}
}View MCP Connection Instructions for more details.
How does an external agent use this tool?
After the external agent is connected to an Agent Group that can use this tool, paste this prompt into the agent:
Agent prompt
Use the AgentPMT-Tool-Search-and-Execution tool. First call action 'get_instructions' so you know how to use the tool search interface. Then call action 'get_schema' with tool_id 6987b3363a2127a981e41238 ("Get Users Current Time / Date"). After reading the schema and any returned instructions, tell me what this tool can do, we are going to be using it
The agent should fetch the tool schema first, collect the required parameters for your request, and then call the tool through AgentPMT.



