Skip to main content
Glama

crime_nearby

Read-onlyIdempotent

Street-level crime within about a mile of a point or postcode for a month (data.police.uk), counts by category and a sample. (cost: 2 credits)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crime_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoYYYY-MM
latitudeNonumber
postcodeNostring
longitudeNonumber

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the safety hints provided in annotations, the description adds important behavioral context regarding the data source, the specific scope (about a mile), and the output granularity (counts by category and a sample). It also specifies the transaction cost.

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?

The definition is highly dense but concise, packing the core function, scope, data source, and limitations into a single, impactful sentence. It avoids unnecessary padding.

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?

Given the scope of the request (location + time + aggregation), the description is largely complete. It clarifies the data source and the nature of the return value (counts/sample), which is sufficient for an agent to formulate a complete request.

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 description coverage is 100%, meaning the schema fully documents the parameters. The description provides no additional semantic meaning to the four required input fields beyond reinforcing the geographical and temporal requirements.

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?

The description clearly states the tool retrieves street-level crime data within a one-mile radius for a specified month, grounding it to a real-world source (data.police.uk). While clear, it could be slightly more explicit about whether it returns aggregated counts or a list of crimes.

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 tool implies usage when a user requests local crime statistics based on a geographic point or postcode and a specific time frame. It does not explicitly guide the agent against using it for broader historical analysis or non-UK locations.

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