list_timezones
List supported timezones + UTC offsets.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Unit & Currency Converter
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses the basic function (listing timezones and offsets) but lacks details on behavioral traits like pagination or auth requirements. The description is minimal but not misleading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no waste. Every word serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters, no output schema, and no annotations, the description is adequate for a simple list tool. It covers the essential information, though it could clarify the output format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so baseline is 4. The description adds no parameter information, but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'List' and the resource 'supported timezones + UTC offsets'. It distinguishes from siblings like convert_timezone and list_units, which have different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description does not provide explicit guidance on when to use this tool versus alternatives. Usage is implied as a simple enumeration, but no when-not-to or context is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool has a distinct purpose: currency conversion, timezone conversion, unit conversion, date difference calculation, and listing supported entities. There is no overlap, so an agent can easily choose the correct tool.
Naming Consistency4/5
Tools follow a consistent verb_noun pattern (e.g., convert_currency, list_timezones). The only minor deviation is 'date_diff' which uses noun_noun, but it is still clear and fits the pattern of other tools.
Tool Count5/5
With 6 tools, the set is well-scoped for a unit and currency converter. It covers all necessary operations without being too sparse or overwhelming.
Completeness5/5
The tools provide full conversion capabilities (currency, timezone, unit), date difference calculation, and listing helpers for timezones and units. There are no obvious gaps for the server's stated purpose.