Skip to main content
Glama

What is at this location

nearby
Read-onlyIdempotent

For a WGS84 point in Ireland: county, local authority, LEA, constituency, electoral division, small area and settlement (GeoHive) with crosswalk codes, the nearest Met Éireann station and forecast, recorded monuments within 500 m (SMR) and NPWS protected sites at the point. Not live observations, river levels, buoys, bikes or populations: use ireland_call for those.

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

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, e.g. 53.3498.
lonYesLongitude, e.g. -6.2603.
hoursNoForecast hours to include.
max_tokensNoResult budget in tokens (default 2000).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -{}New value: +true
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it identifies the data sources, the 500 m monument search radius, the point-based NPWS lookup, and the exclusion of live or dynamic data. It does not detail response shape or rate limits, but those are partly covered by the output schema and rich annotations.

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

Conciseness5/5

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

The description is front-loaded with the core scope and then lists the returned resource categories efficiently. The second sentence delivers the exclusion guidance with no wasted wording. Despite its density, every phrase contributes to selecting or correctly interpreting the tool.

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 a full output schema and rich annotations already present, the description supplies the remaining critical context: CRS and country applicability, exact returned datasets, the 500 m search radius, and explicit exclusions routed to ireland_call. Nothing an agent needs in order to select and invoke this tool correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all four parameters. The description still adds meaning by specifying WGS84 coordinates and Ireland as the geographic applicability, which is more than the schema's example-based descriptions provide. It does not explain hours or max_tokens directly, but the forecast mention implies the hours parameter and the schema covers the rest.

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 gives a specific lookup action for a WGS84 point in Ireland and enumerates the exact resources returned: administrative boundaries, crosswalk codes, nearest Met Éireann station and forecast, monuments within 500 m, and NPWS protected sites. It also distinguishes the tool from nearby alternatives by naming ireland_call for live observations, river levels, buoys, bikes, and populations.

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?

It clearly states the usage context: a WGS84 point in Ireland. It also states what not to use it for and names ireland_call as the alternative for live observations, river levels, buoys, bikes, and populations. It does not explicitly discuss when to choose this over other siblings such as search or ireland_resolve_place, but the primary routing guidance is explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.