Skip to main content
Glama

UK property & area data

UK Police Data: Crime categories

uk-police__categories
Read-onlyIdempotent

Valid crime categories for a month. Free within the daily allowance, then $0.001 USDC per call via x402.

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": "uk-police__categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoMonth as YYYY-MM (default: latest)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new operational context: free within a daily allowance, then $0.001 USDC per call via x402, which affects how an agent should budget calls. It stops short of 5 because nothing is said about caching/refresh cadence or how up-to-date the category set is.

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?

Two short sentences with no filler; the functional purpose leads and the cost model follows. Every clause carries information an agent can act on.

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?

An output schema exists, so return values need not be described, and the single optional parameter is fully documented. The remaining gap is relational: the description never says how these categories connect to the crime/outcome tools that likely consume them.

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 100% and the schema already documents 'Month as YYYY-MM (default: latest)', so the description's 'for a month' adds no format detail beyond it. Baseline 3 is appropriate when the schema fully carries parameter meaning.

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 the resource clearly ('crime categories') and scopes it by month, so an agent can tell it apart from the crime-listing siblings. The verb is only implied (list/get), and there is no explicit contrast with tools like uk-police__crimes-at-location, so it falls short of a 5.

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?

No guidance on when to call this versus alternatives — e.g. whether it is a prerequisite lookup for the crime endpoints or a standalone reference. The only context given is billing, not selection criteria.

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