Skip to main content
Glama

Apply a Mud Run code

apply_mud_run_code
Idempotent

Put the customer's own Mud Run code on their Full detail: 10% off the detail (their first Full detail only).

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": {
      "link": "<link>"
    },
    "name": "apply_mud_run_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe private change-or-cancel link from the customer's confirmation email (or from request_booking).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare a non-readonly, idempotent, non-destructive mutation, and the description is consistent with that, so the safety profile is covered. It adds one useful behavioral fact beyond annotations — the discount applies only to the first Full detail — but says nothing about failure modes (invalid, expired, or already-redeemed code) or whether the discount is re-priced into an existing quote.

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?

One front-loaded sentence with the action first and the qualifier after the colon; no filler. The colon-and-parenthetical construction is slightly run-on but every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, mutation-flagged tool with no output schema, the description covers what the tool does and the key eligibility rule, which is adequate. It is not complete: the return value (does it confirm the discount, return a new total, or fail silently?) and preconditions such as the booking state are unaddressed.

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% and the single parameter (a private change-or-cancel link) is fully documented, so the baseline is 3. The description adds no clarification of the link and, if anything, creates ambiguity by speaking of the customer's "code" while the only input is a link — an agent may momentarily expect a code argument.

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?

States a specific verb and object ("Put the customer's own Mud Run code on their Full detail") plus the concrete effect (10% off the detail, first Full detail only), which is enough to separate it from the booking-management siblings. Domain jargon ("Mud Run", "Full detail") is unexplained, but the discount outcome makes the intent recoverable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The eligibility constraint "their first Full detail only" implicitly tells the agent when the tool is applicable, which is real usage guidance. However, it never says when not to use it, what to do instead if the customer has no code, or how it interacts with quote/booking flows, leaving the agent to infer the trigger conditions.

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