Skip to main content
Glama
Sign In

Agent Data Tools

by io.github.Nutshell2000
OverviewDiscussionsAdmin

Geocode an address, coordinates: place or address name to latitude and longitude

geocode_address
Read-only

Geocode a place or address to latitude and longitude: a city, town, landmark or address name becomes coordinates, with country, region, population and elevation where known, best match first (Wikidata, CC0). Use to turn a place name into coordinates for maps, distance, weather or routing. Example: name=Uppsala. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "geocode_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPlace name
countNoMax results (1-10, default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly/destructive/openWorld, yet the description adds substantial new context: the upstream data source and license (Wikidata, CC0), result ordering ('best match first'), which fields may come back (country, region, population, elevation), and the billing model ($0.002/call, first 25 free, failed calls free). The note that repeats are not free operationalizes idempotentHint=false in concrete terms.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and inputs, then use cases, then cost and safety notes. It is slightly overstuffed: the opening clause largely restates the title, and the billing point is made twice ('charged per call' and 'repeats are not free').

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?

With no output schema, the description helpfully names the returned fields, and pricing plus the read-only guarantee cover the operational concerns. It does not specify the coordinate representation (lat/lon order, decimal precision) or failure behavior beyond 'failed calls free', which leaves a small gap for a tool returning coordinates.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented by the schema, and the description adds little parameter-level detail. The example (name=Uppsala) and 'best match first' give mild ordering context for count, but no format guidance such as coordinate ordering or precision.

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?

States a specific verb and resource ('Geocode a place or address to latitude and longitude') and enumerates accepted inputs (city, town, landmark, address name). The forward direction is clear enough to distinguish it from the sibling geocode_reverse without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names downstream uses ('for maps, distance, weather or routing') and provides a worked example (name=Uppsala), which gives an agent clear context for selecting it. It stops short of an explicit exclusion like 'use geocode_reverse to go from coordinates back to a place', so the alternative is only implied by the sibling name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Data Tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources