Skip to main content
Glama

Find a council PCN code

search_contravention_codes
Read-onlyIdempotent

Find council penalty charge notice contravention codes from plain words, e.g. "disabled bay", "yellow box junction" or "dropped kerb". Returns each code, its description and its charge level; use explain_contravention_code for more.

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": {
      "query": "<query>"
    },
    "name": "search_contravention_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many codes, 1 to 10. Default 5.
queryYesWhat happened or what the sign or marking was, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds value beyond them by disclosing the return shape — each code, its description and its charge level — which matters because no output schema exists, and by pointing to the drill-down tool.

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?

A single front-loaded sentence plus one short follow-up clause. The examples do real work illustrating the expected input, and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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-only search with full schema coverage and no output schema, the definition supplies the purpose, input style, return contents and the follow-up tool. Nothing an agent needs to call it correctly is missing.

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%: both query and limit are fully documented in the schema, including the 1–10 range and default of 5. The description reinforces that query should be plain words with examples, but adds no syntax or formatting detail beyond that, so the baseline 3 applies.

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 ("Find council penalty charge notice contravention codes") plus the input modality ("from plain words") with three concrete example queries. It also names the sibling tool that covers the deeper follow-up need, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines4/5

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

Makes clear this is the lookup tool for plain-language descriptions of a situation, sign or marking, and routes to explain_contravention_code when more detail is wanted. It stops short of stating explicit exclusions (e.g. don't use for looking up a code you already know), so it falls just short of a 5.

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.