Skip to main content
Glama

Parking Fine Appeal Check

fine_appeal_check
Read-onlyIdempotent

Checks how strong the grounds to appeal a parking fine or parking charge look, from yes/no answers (signs, markings, payment machine, notice details, valid ticket or permit, owner or keeper, mitigating circumstances, evidence). Returns likely grounds, where to send the appeal in that country, a deadline note and links to the Appeal Calculator and sample letters. Use this when someone asks about appealing, disputing or challenging a parking fine, ticket, citation, PCN or private parking charge, or about their chances of winning. All inputs are optional: pass what the driver has said and the country. General information, not legal advice.

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

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter country code where the fine was issued (AU, US, GB, CA, NZ, IE or other).
evidenceNo
mitigatingNo
issuer_typeNounknown
signs_clearNo
markings_clearNo
details_correctNoAre the registration, place, date and offense on the notice correct?
machine_workingNo
valid_ticket_or_permitNo
were_you_the_owner_or_keeperNoWas the person the owner or registered keeper at the time?

Output Schema

NameRequiredDescriptionDefault
linksYes
groundsYes
summaryYes
strengthYes
next_stepNo
disclaimerNo
answers_usedNo
deadline_noteNo
evidence_tipsNo
where_to_sendNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "answers_used": {
      +      "type": [
      +        "object",
      +        "array"
      +      ]
      +    },
      +    "deadline_note": {
      +      "type": "string"
      +    },
      +    "disclaimer": {
      +      "type": "string"
      +    },
      +    "evidence_tips": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "grounds": {
      +      "items": {
      +        "properties": {
      +          "ground": {
      +            "type": "string"
      +          },
      +          "strength": {
      +            "type": "string"
      +          },
      +          "why": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "links": {
      +      "properties": {
      +        "appeal_calculator": {
      +          "type": "string"
      +        },
      +        "fines_guide": {
      +          "type": "string"
      +        },
      +        "sample_letters": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "strength": {
      +      "type": "string"
      +    },
      +    "summary": {
      +      "type": "string"
      +    },
      +    "where_to_send": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "links",
      +    "strength",
      +    "summary",
      +    "grounds"
      +  ],
      +  "type": "object"
      +}
  2. First observed

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, non-destructive and closed-world, so the safety profile is covered. The description adds context beyond them: it discloses the return payload (likely grounds, where to send the appeal in that country, a deadline note, links), states that all inputs are optional, and carries a 'general information, not legal advice' disclaimer — a meaningful caveat for a consumer-facing assessment 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?

A single dense paragraph that front-loads what the tool does and returns before moving to when-to-use, inputs, and the disclaimer. Slight redundancy in re-listing inputs already visible in the schema, but that listing earns its place given the low schema coverage.

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 10-parameter tool with an output schema and full annotations, the description covers purpose, trigger conditions, input expectations, output shape and a legal disclaimer. The main gap is behavior with sparse input — what the assessment reports when only country is supplied — which is the likely real usage given all params are optional.

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 description coverage is only 30%, so the description must carry weight, and it does by restating the parameter concepts in plain language (signs, markings, payment machine, notice details, valid ticket or permit, owner or keeper, mitigating circumstances, evidence) plus country. It also clarifies that every input is optional, which matters for partial answers. It stops short of explaining the enum choices or how 'unsure' is treated.

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 — checking how strong the grounds to appeal a parking fine or parking charge look — and enumerates the yes/no inputs it reasons over (signs, markings, payment machine, notice details, ticket/permit, owner/keeper, mitigating circumstances, evidence). This is clearly distinguished from siblings like search_parking or get_listing, which deal with finding or viewing parking rather than assessing appeal strength.

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?

Gives an explicit trigger set with synonyms: 'appealing, disputing or challenging a parking fine, ticket, citation, PCN or private parking charge, or about their chances of winning.' It does not state when NOT to use it or name a sibling to prefer, though mentioning the Appeal Calculator and sample letters as outputs implies those are separate downstream tools.

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