Skip to main content
Glama

Airsockfly

Accept price change

accept_price_change

Accept the changed price of an order after create_booking returned price_changed, and continue to payment.

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

Input Schema

NameRequiredDescriptionDefault
orderIdNoOrder identifier from list_bookings or create_booking.
idempotencyKeyNoUnique key of 8 to 100 characters that you generate once per attempt. Repeating it never creates a duplicate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already disclose that this is a non-read-only, non-destructive, closed-world mutation. The description adds useful workflow context by saying it continues to payment, but it does not explain irreversibility, retry behavior, or what happens to the original price change beyond the precondition.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no redundant wording. It packs the trigger, action, and next step efficiently.

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 simple mutation tool with full schema coverage, annotations, and no output schema, the description provides the key workflow trigger and outcome. It could be slightly more complete by clarifying retry or idempotency behavior explicitly, but the schema already covers the idempotency key.

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%, so both orderId and idempotencyKey are already documented in the input schema. The description adds only the general notion that the action concerns an order and does not contribute parameter-level details beyond the schema.

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?

The description states a specific verb and resource: accepting the changed price of an order. It also names the exact triggering condition, create_booking returning price_changed, and the follow-on outcome, continuing to payment, which distinguishes it clearly from sibling booking tools.

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?

It gives clear when-to-use guidance tied to a concrete event: after create_booking returns price_changed. It does not state when not to use it or name alternative tools for other price-related flows, so it falls short of the fullest rubric level.

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