Skip to main content
Glama

Search the parking ticket guides

search_guides
Read-onlyIdempotent

Search ByeFine's plain-English guides to UK parking tickets and other penalty notices (council penalty charge notices, private parking charges, bus lanes, a Notice to Owner, a refused appeal, the independent adjudicators, and more). Returns the best matches with a slug for get_guide. General information for England and Wales, not legal advice.

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_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches, 1 to 10. Default 5.
queryYesWhat to look for, in plain words, e.g. "private parking charge" or "notice to owner".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: jurisdiction (England and Wales), the non-legal-advice disclaimer, and the shape of the return (best matches plus a slug). It does not discuss ranking, tie-breaking, or what happens with zero matches, which would be the next layer of detail.

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?

Two sentences, front-loaded with what is searched before the return-value and disclaimer notes. The long parenthetical topic list is information-dense rather than decorative, though it could be trimmed without much loss.

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 two-parameter search with no output schema, the description covers the domain, jurisdiction, disclaimer, return shape, and downstream tool. An agent knows enough to call it correctly. Only the empty-result and ranking behavior remain unstated.

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%, and the schema itself supplies both the query example ('private parking charge', 'notice to owner') and the limit bounds with a default of 5. The description's parenthetical topic list loosely hints at useful query terms but adds no syntax, format, or ranking semantics beyond the schema, so the baseline of 3 applies.

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?

Description names a specific verb and resource — searching ByeFine's plain-English guides — and enumerates the covered topics (council PCNs, private parking charges, bus lanes, Notice to Owner, refused appeals, adjudicators). It clearly separates itself from get_guide by saying results come back with a slug for that tool, but it never mentions list_guides, so the search-vs-browse distinction is only partially drawn.

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?

The phrase 'Returns the best matches with a slug for get_guide' gives a clear two-step workflow: search here first, then fetch the full guide. It also sets scope expectations with 'General information for England and Wales, not legal advice.' What's missing is an explicit exclusion telling the agent when to use list_guides instead of searching.

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.