[duvera · risk:low] Convert a city or place name (e.g. "Berlin", "San Francisco") to latitude/longitude, country, timezone, and population. Use this before weather.current or weather.air-quality when you only have a place name. No account required.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Place name to look up, e.g. "Berlin" or "Springfield, Illinois". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the tool is a geocoding lookup (read operation) with 'No account required', but does not explicitly state read-only behavior or lack of side effects. The description adds useful context beyond the schema.
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 two sentences with no wasted words. The first sentence defines purpose and outputs, the second gives usage guidance and a notable feature. Every sentence adds value.
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?
Despite no output schema, the description lists the key output fields. The parameter is fully documented. It connects to sibling weather tools and includes a risk label. The description is complete for a simple geocoding tool.
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 covers the single parameter 'query' with a description. The tool description adds examples and mentions output fields, but does not significantly enhance understanding of the parameter itself beyond what the schema already provides. Schema coverage is 100%, 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 clearly states the verb 'Convert' and the resource 'city or place name to latitude/longitude, country, timezone, and population'. It also gives concrete examples ('Berlin', 'San Francisco') and distinguishes from sibling tools by recommending its use before weather tools.
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 explicitly advises using this tool before 'weather.current' or 'weather.air-quality' when only a place name is available, providing clear usage context. It also notes 'No account required', but does not explicitly state when not to use the tool.
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 is prefixed with its service name, and within each service, tools have distinct actions (e.g., mail_read vs. availability_find). The duvera tools cover different subdomains like dev, finance, and food with no overlap, making selection unambiguous.
All tools follow the pattern service__action_object or service__category_action, using lowercase with underscores. The order of verb and noun varies slightly (e.g., package_track vs. boardingpass_show), but the naming is highly predictable and readable.
With 52 tools, the server is large but justified as a gateway aggregating many external services. Each tool corresponds to a common task for its service, so no tool feels extraneous, though the total number is high.
The tool surface covers a wide array of services but only provides one or two basic operations per service (mostly read-only). While this suits a quick-lookup gateway, deeper workflows (e.g., creating or updating resources) are missing, leaving gaps for many use cases.
