Get the current time for a specified UTC offset. Provide an offset like '+08:00' to retrieve the exact local time.
Get current time for UTC offset (e.g. '+08:00' or '-05:00').
| Name | Required | Description | Default |
|---|---|---|---|
| utc_offset | Yes | UTC offset string (e.g. '+08:00' or '-05:00') |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a non-destructive read of 'current time', but discloses nothing about the return format, whether a date is included, or any locality/timezone semantics. Only the most obvious trait is conveyed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, front-loaded with the action and immediately followed by the required input format. No filler, no restated title, nothing that fails to earn its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, schema-complete tool with no output schema, the description is adequate but leaves the response shape undefined (time only? offset echo? date?). It does usefully clarify that the input is an offset rather than a place name, which is the main ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single parameter is fully documented there. The description repeats the same '+08:00' / '-05:00' example verbatim, adding no syntax, validation, or edge-case detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get current time') plus the exact input shape (UTC offset), so the agent knows precisely what the tool yields. It does not need sibling differentiation since no sibling in the list (weather, finance, sports, web-search) overlaps with time lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: the offset example suggests the tool is for looking up the time at a given offset rather than at a named city or timezone. There is no explicit when-to-use guidance, no statement of when this is preferable to alternatives, and no exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.