Skip to main content
Glama

Explain a council PCN code

explain_contravention_code
Read-onlyIdempotent

Explain a council penalty charge notice contravention code (the two-digit code on the PCN, with any suffix letter): what it means, whether it is a higher or lower level contravention, what any suffix means, and the grounds the law allows for formal representations in England. No amounts: those depend on the council and are printed on the notice. Private parking charges do not use these codes.

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": {
      "code": "<code>"
    },
    "name": "explain_contravention_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code as printed, e.g. "01", "12r" or "31J".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description does not need to restate safety. It usefully adds that amounts are deliberately omitted because they are council-dependent and printed on the notice, plus the England-only legal scope, but says nothing about response shape or length beyond the topic list.

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 dense lead sentence carrying the full payload, followed by two short boundary clauses. Nothing is repeated from the schema or annotations, and the most important information (what the code means and the legal grounds) comes first.

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?

With one fully documented parameter, no output schema, and strong annotations, the description covers what an agent needs: input format, answer contents, jurisdictional limit, and what is deliberately excluded. Only the granularity of the returned grounds and level classification is left unspecified, which is minor.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a clear format example, so the baseline is 3; the description earns a point by explaining that the input is the two-digit PCN code plus any suffix letter and that suffix handling is part of the answer's job. That clarifies the accepted input domain beyond the raw string type.

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 precise verb and resource ('explain a council penalty charge notice contravention code') and enumerates exactly what the answer contains: meaning, higher/lower level, suffix meaning, and statutory grounds for representations. The scoping clauses ('No amounts', 'Private parking charges do not use these codes') make the boundary of the resource unmistakable.

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?

Explicit exclusions tell the agent when not to rely on it for monetary amounts and when the domain is out of scope (private parking charges). It does not name a sibling for adjacent needs such as deadlines or locating a code, so routing guidance is implied rather than spelled out.

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.