Skip to main content
Glama

Check a notice (free)

check_notice

Send a photo or PDF of a UK parking ticket or other penalty notice (parking, bus lane, road charges, rail, tram and bus penalty fares, tolls, and other penalties with a written way to challenge them; a police ticket such as speeding, a red light, a phone or insurance is written as a letter the driver sends themselves). ByeFine reads it and says, free, whether it is worth challenging and why. It does not handle court papers. Give either file_url (https) or file_base64 with mime.

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": "check_notice"
  }
}

Input Schema

NameRequiredDescriptionDefault
mimeNoThe file type, with file_base64.
nameNoA file name, optional.
file_urlNoAn https address of the photo or PDF.
file_base64NoThe file's bytes, base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare openWorldHint=true, readOnlyHint=false, idempotentHint=false, and destructiveHint=false, and the description adds genuinely new behavioral context: the check costs nothing, it accepts photo or PDF, and it will not process court papers. It does not mention size limits, data retention/privacy of an uploaded document, or what happens on unreadable input, which are the remaining gaps for an upload-and-analyze tool.

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?

Front-loaded with the core action and benefit ('Send a photo or PDF... ByeFine reads it and says, free, whether it is worth challenging'), then constraints. The long parenthetical enumerating covered notice types is informative but heavy, and the police-ticket clarification is dense; it earns most of its length but could be tightened.

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 four-parameter, no-output-schema tool, the description covers the input mechanics, the exclusions, and the nature of the result (a free challenge-worthiness verdict with reasons). What is missing is operational detail on file limits and failure behavior, which matters for a document-upload tool but does not block correct invocation.

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% so the baseline is 3, but the description adds real meaning by stating the mutual-exclusivity rule ('Give either file_url (https) or file_base64 with mime') that the schema itself does not express. The https requirement for file_url and the pairing of mime with base64 are both clarified beyond the raw property descriptions.

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 action (send a photo/PDF, ByeFine reads it) and a specific resource (UK parking ticket or penalty notice), plus the concrete output: a free assessment of whether it is worth challenging and why. It also carves out the scope boundaries (court papers excluded; police tickets handled as self-written letters), so an agent can distinguish it from siblings like calculate_deadlines or go_ahead.

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?

Clear context for when to call it: the user has a UK penalty notice and wants a free challenge assessment, explicitly stated as free. It also specifies a when-not ('It does not handle court papers') and excludes police tickets handled as driver-written letters. No named alternative sibling is offered for the excluded cases, which keeps it 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.