Skip to main content
Glama

Vehicle crime near a postcode

vehicle_crime_near
Read-onlyIdempotent

Latest month of police-reported vehicle crime near a UK postcode, with the most affected streets.

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": {
      "postcode": "<postcode>"
    },
    "name": "vehicle_crime_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeYesUK postcode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 non-open-world behavior, so safety is covered. The description adds genuinely useful behavioral context beyond them: the data is police-reported, limited to the latest month, and includes 'the most affected streets'. It does not say how large the 'near' radius is or what happens with an invalid postcode.

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?

One sentence, front-loaded with the resource and recency, ending with the notable output detail. No filler, no restatement of the title, nothing that could be cut.

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 one-parameter lookup with full annotation coverage and no output schema, the description supplies the essentials: data source, time window, and headline content. The main residual gap is the undefined search radius around the postcode, which affects interpretation of results.

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?

With a single parameter at 100% schema description coverage, the schema already documents the postcode field. The description adds only the word 'near', which implies a proximity radius the schema does not define and the description does not quantify. Baseline 3 is appropriate.

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 resource (police-reported vehicle crime) with explicit scope: 'near a UK postcode' and 'latest month'. An agent knows exactly what data comes back, though the description never distinguishes this from adjacent location-based siblings such as road_closures or ulez_check.

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: the phrase 'latest month' signals this returns only the most recent period, so it is not a historical trend tool. There is no explicit when-to-use statement, no exclusions, and no named alternative for historical crime data or for other location checks.

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