Skip to main content
Glama

Find nearby Notting Hill places

nearby_places
Read-onlyIdempotent

Nearest curated Notting Hill places to a WGS84 coordinate supplied in the request, with distance in metres.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "nearby_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax places to return (default 10)
radiusNoSearch radius in metres (default 500)
categoryNo
latitudeYes
longitudeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds useful behavioral context — that results are curated places, coordinates are WGS84, and distances are in metres — but says nothing about ordering, default radius behavior, or what happens when nothing falls in range.

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?

A single dense sentence with the key facts (proximity, scope, coordinate system, distance unit) front-loaded and no filler. It could be slightly clearer with a brief clause on ordering or defaults, but nothing is wasted.

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

Completeness3/5

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

No output schema exists, so the description should carry more of the return/behavioral burden. It omits result ordering, what 'curated' excludes, whether distance is computed from the supplied point, and how category filters results — gaps that matter for a 5-parameter geo query tool.

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 only 40%: only limit and radius have descriptions, while category and the two coordinates are undocumented in the schema. The description partially compensates by pinning the coordinate system (WGS84) and the distance unit (metres, tying to radius), but the category enum and its effect on results are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific action and resource: nearest curated Notting Hill places to a WGS84 coordinate, returning distance in metres. This is clearly distinct from get_place or compare_places in spirit, but it never explicitly contrasts with the closest sibling, search_places, which likely overlaps in intent.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives among the six siblings. An agent must infer from the name alone whether to call nearby_places, search_places, or list_places for a given lookup.

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.

Resources