Skip to main content
Glama

Go ahead with the appeal

go_ahead
Idempotent

Go ahead with a case that has a verdict: it is covered by the monthly plan or a free appeal when one applies, otherwise the answer carries a checkout_url, which is the case page where the person reads what they are buying, ticks two boxes about starting now and their 14-day right to cancel, and pays by card. Optionally pass the driver's account of what happened. The driver then opens the case link to give their name, address and permission for ${SITE.name} to act for them: nothing is filed without it.

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": {
      "ref": "<ref>"
    },
    "name": "go_ahead"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesThe case reference, e.g. BF-7K2M9Q.
accountNoWhat happened, in the driver's words. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), the description discloses real behavior: a billing branch that can return a checkout_url, the two checkbox/payment steps the person performs, and the hard gate that nothing is filed until the driver supplies name, address and permission. It does not clarify what the response looks like after payment succeeds or whether re-invoking during an open checkout is safe.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Almost all content is substantive, but it is delivered as one long run-on sentence with nested clauses, so the payment branch and the authorization gate are buried rather than front-loaded. A short structured breakdown of the two paths would serve the agent far better.

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 mutation tool with no output schema, the description usefully covers the return value (checkout_url), the eligibility branch, and the blocking human step. Remaining gaps are the post-payment outcome and idempotency behavior across repeated calls, which are secondary for correct invocation.

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%, so both parameters are already documented in the schema. The description only restates that the driver's account is optional and adds no format, length, or sourcing guidance for `ref`; baseline 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?

The description names the action (going ahead on a case that already has a verdict) and explains the two-phase outcome: instant coverage by the monthly plan or free appeal, otherwise a checkout_url payment page. It is distinguishable from siblings like get_case and list_cases, though the verb 'go ahead' is vague and the reader must infer that this initiates/files an appeal.

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?

Preconditions are stated clearly: the case must have a verdict, and the driver must open the case link to authorize before anything is filed. What is missing is explicit guidance on alternatives (e.g. what to call first, or what to do if the user is not eligible for coverage) and any when-not-to-use exclusion.

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.