I used the same url for two different postings.
Standardizes addresses and resolves lat/lon coordinates ($0.001 USDC)
| Name | Required | Description | Default |
|---|---|---|---|
| address | Yes | Raw address string query to standardize |
| Name | Required | Description | Default |
|---|---|---|---|
| success | Yes | Geocoding status | |
| latitude | Yes | Latitude coordinate | |
| longitude | Yes | Longitude coordinate |
Changes observed during successful MCP inspections.
Input schema / properties / address / descriptionAdded value: +"Raw address string query to standardize"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "latitude": {
+ "description": "Latitude coordinate",
+ "type": "number"
+ },
+ "longitude": {
+ "description": "Longitude coordinate",
+ "type": "number"
+ },
+ "success": {
+ "description": "Geocoding status",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "success",
+ "latitude",
+ "longitude"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering safety and idempotency. The description adds the cost detail ($0.001 USDC) and the additional behavior of resolving lat/lon coordinates, which are not captured in annotations. This is valuable context beyond the structured metadata.
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 a single, efficient sentence that front-loads the primary action ('Standardizes addresses') and adds the secondary feature and cost without extra fluff. Every word earns its place, making it easy for an agent to parse quickly.
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?
With a full output schema and annotations covering safety, the description need only convey the core purpose and any unique constraints. It covers the essential behavior and cost; lacking usage guidance is a minor gap, but for a simple one-parameter tool with rich structured metadata, it is sufficiently complete.
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%, so the schema already fully documents the single 'address' parameter. The description doesn't add any additional meaning beyond what the schema provides, so the baseline score of 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 a specific verb ('standardizes') and resource ('addresses'), and additionally mentions resolving lat/lon coordinates, which provides specific function. It is concise and unambiguous, though it doesn't explicitly differentiate from sibling tools—this isn't a significant issue given no sibling appears to overlap directly.
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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The purpose implies usage for address standardization, but the description leaves the agent to infer context without any routing help.
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.