Ground elevation in metres for a place name. (Free. This server also sells a paid API — call paid_catalogue for the routes and prices; x402 over USDC on Base, no signup.)
| Name | Required | Description | Default |
|---|---|---|---|
| location | Yes | Place name |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It states the output unit but does not disclose behavior for invalid or missing locations, accuracy, or response structure. The mention of the paid API adds cost context but not operational behavior.
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?
The description is concise, with a clear main clause and a parenthetical note. The parenthetical about the paid API is slightly tangential but does not bloat the overall length.
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?
Given the simple single-parameter tool and no output schema, the description covers the core purpose and unit. It lacks explicit return format information, but the simplicity and sibling context keep this from being a major gap.
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?
The schema already fully describes 'location' as a place name, and the description merely echoes that. No additional meaning is added beyond what the schema provides, so baseline 3 is appropriate.
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?
The description states a specific resource (ground elevation) and output unit (metres) for a place name, clearly distinguishing it from sibling tools like geocode or air_quality. The verb is implicit but the purpose is unmistakable.
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?
The description clearly implies the use case: when you need elevation for a place name. It does not explicitly name alternatives, but the context is specific enough that an agent can determine when to select it. The note about free/paid API provides extra context but not exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct purpose (air quality, country indicators, earthquakes, elevation, geocode, holidays, URL reading, web search, catalogue). The only overlap is that geocode already returns elevation, making the separate elevation tool redundant and potentially confusing.
All tool names follow a consistent lowercase snake_case pattern, mixing noun-based names (earthquakes, elevation) and verb_noun names (read_url, web_search). The style is uniform across the set, so naming is predictable and readable.
Nine tools is a reasonable count for a general-purpose data/web utility server. However, the set feels like a random assortment of free APIs rather than a coherent scoped collection, which slightly undermines the sense of appropriateness.
The server name 'tokenguard' implies a focus on token safety and blockchain intelligence, but the free tools cover unrelated domains (air quality, geocoding, holidays, web). The actual token-safety features are only mentioned in the paid_catalogue and are not exposed as MCP tools, leaving a significant gap between the server's apparent purpose and its actual capabilities.