Skip to main content
Glama

streetview_coverage

Checks whether Google Street View has a panorama near an OS grid reference within a chosen radius, returning panorama location, capture date, distance, and bearing.

Instructions

Check whether Google Street View has a panorama near a grid reference.

Uses the free metadata endpoint, so it costs nothing. Returns the panorama location, capture date, and distance/bearing to the grid reference point.

Args: grid_ref: OS grid reference, e.g. "SU 123 456". radius_m: how far from the point to search for a panorama (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": {
      "grid_ref": "<grid_ref>"
    },
    "name": "streetview_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
grid_refYes
radius_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real traits: the call is quota-free and it returns location, capture date, and distance/bearing. It omits what happens when no panorama exists (null result vs error), whether an API key is needed, and any rate limiting, which matters for a tool whose whole purpose is a yes/no check.

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?

Front-loaded with the purpose in the first sentence, then cost, then return values, then params. The Args block restates parameter names but earns its place by supplying the format example the schema lacks; no sentence is filler.

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?

For a simple two-parameter read tool with no output schema, the description explains what comes back and what the call costs. The one meaningful gap is the negative case — what a miss looks like — which an agent calling an availability check would want to know.

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 0%, so the description must compensate, and it does: grid_ref is given a concrete format example ('SU 123 456') and radius_m is defined in metres as the search distance. Only the default radius value is left to the schema, which already carries it.

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?

States a specific verb and resource: 'Check whether Google Street View has a panorama near a grid reference', with the scope (proximity search around a point) made explicit. It does not differentiate itself from the sibling 'streetview_from_gridref', so an agent must infer whether this is the availability check and the other the fetch.

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

Usage Guidelines3/5

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

The note that it 'uses the free metadata endpoint, so it costs nothing' implies it is the cheap pre-check before a costlier call, but the description never says when to prefer it over 'streetview_from_gridref' or states any exclusion. Usage is implied rather than instructed.

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