Skip to main content
Glama

streetview_from_gridref

Fetches Google Street View images for an Ordnance Survey grid reference by locating the nearest outdoor panorama within a set radius and returning views aimed at the referenced point.

Instructions

Fetch Google Street View image(s) for an OS grid reference.

Finds the nearest outdoor panorama within radius_m of the centre of the grid square, then returns the image(s). By default one image is taken looking from the panorama towards the grid reference point.

Args: grid_ref: OS grid reference, e.g. "SU 123 456" or "NN166712". views: number of images spread evenly around 360 deg (1-8). 4 gives N/E/S/W-style coverage. heading: compass heading of the first view in degrees. Default: towards the point (or 0 if the panorama is on top of it). pitch: up/down camera angle, -90 to 90. fov: horizontal field of view in degrees, 10-120. radius_m: search radius for the nearest panorama in metres. size: image size "WxH", max 640x640. save: also save JPEGs to REFCONV_OUTPUT_DIR and return their paths.

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_from_gridref"
  }
}

Input Schema

NameRequiredDescriptionDefault
fovNo
saveNo
sizeNo640x640
pitchNo
viewsNo
headingNo
grid_refYes
radius_mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does well: it discloses the nearest-panorama search within radius_m, the default camera orientation logic (towards the grid ref, or 0 if the panorama sits on the point), and the side effect that `save` writes JPEGs to REFCONV_OUTPUT_DIR and returns their paths. It omits what happens when no panorama is found within the radius and any auth/rate-limit context, which are the remaining behavioral gaps.

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 summary sentence followed by a structured Args block; nearly every line carries information. The docstring format is slightly verbose but no sentence is filler, and the search-then-render sequence is ordered logically.

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 an 8-parameter tool with no annotations and no output schema, the description covers behavior, parameter ranges and the save side effect well. The main omissions are failure behavior when no panorama exists within radius_m and any indication of the returned image format/structure beyond saved file paths.

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

Parameters5/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 entirely, and it does: every one of the 8 parameters gets meaning plus constraints (views 1-8 with 4 = N/E/S/W coverage, pitch -90 to 90, fov 10-120, size max 640x640, grid_ref accepted formats with examples). This is meaningfully richer than the bare schema types and defaults.

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 ('Fetch Google Street View image(s) for an OS grid reference') and immediately qualifies the retrieval mechanism (nearest outdoor panorama within radius_m of the grid square centre). This is clearly distinguishable from the coordinate-conversion and coverage siblings without needing their schemas.

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?

Usage is only implied through the described behavior — an agent can infer this is the tool for actually getting imagery rather than coverage metadata or coordinate conversion, but no alternative is named and no when-not-to-use condition is given. No guidance on prerequisites such as API key or quota availability.

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