Running Cat Geo

Where a point is

where_is

Read-only

Names a point: country, region, town and nearest place, the administrative areas it lies in, and its IANA time zone with the UTC offset now. Use it for "where is this" and "what time is it there"; use point_report when weather, air or rivers are wanted too. It does not search places by name. Counts as one request.

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": {
      "lon": "<lon>",
      "lat": "<lat>"
    },
    "name": "where_is"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Latitude
`lon`	Yes	Longitude
`lang`	No	Language for the names (name:xx in OpenStreetMap, country names translated; the local name where there is none), such as en, de, pl; local names by default

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the quota-relevant fact 'Counts as one request' and the scope limit on name lookup, which are real operational details not in the annotations. It stops short of describing fallback behavior when a point has no nearby named place or how the time zone is derived, so it is strong but not exhaustive.

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?

The return contents are front-loaded, followed by usage, alternatives and the request cost—every sentence carries information. The first sentence is a long compound list that takes a second pass to parse, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only two required numeric parameters, the description does the work of describing the response payload in concrete terms and adds the sibling routing and cost note. An agent has everything needed to call it correctly and to know what it will get back.

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%: lat, lon and lang are each documented with type, range and regex constraints, including the lang pattern and the local-name default. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 opens with a specific verb and resource: it 'names a point' and enumerates exactly what comes back (country, region, town, nearest place, administrative areas, IANA time zone with current UTC offset). It also delimits itself negatively ('does not search places by name'), so an agent can distinguish it from area_report and a name-search tool without opening any schema.

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

Usage Guidelines5/5

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

It gives explicit trigger phrases ('where is this', 'what time is it there') and names the alternative, point_report, with the condition that selects it ('when weather, air or rivers are wanted too'). The exclusion of name-based search closes the most likely misuse path.

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

All Running Cat Geo tools Inspect

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

Need Help?