Skip to main content
Glama

Lock this quote

evuun_book
Idempotent

Lock this exact quote into an arrangement and return the arrangement with a link the person opens to stamp and pay themselves. The agent never pays here.

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": {
      "search_id": "<search_id>",
      "offer_id": "<offer_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "evuun_book"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
offer_idYes
search_idYes
arrangement_idNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, open-world, idempotent, non-destructive), so the description's job is to add context — and it does: it discloses the human-in-the-loop handoff and that the returned arrangement link is what the person stamps and pays with. It does not explain what 'locking' does to the quote (hold, expiry, staleness) or how idempotency behaves on retry, which keeps it from a 5.

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?

Two tight sentences with the action and result front-loaded and the key constraint ('the agent never pays here') placed last for emphasis. Nothing is redundant.

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?

It covers the outcome and return value (arrangement plus link), which matters since no output schema exists. However, for a booking mutation with five undocumented parameters, it says nothing about failure modes such as an expired quote or a mismatched offer, leaving real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must carry the load and largely does not. 'This exact quote' hints that search_id plus offer_id pin the quote and 'return the arrangement' hints at arrangement_id, but idempotency_key, title, and the required/optional split are never explained.

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?

Uses a specific verb+resource pair: locks a quote into an arrangement and returns it with a payment link. The two-phase outcome (agent books, person pays) is concrete enough to distinguish this from read-only siblings like evuun_find or evuun_open, though no sibling is named explicitly.

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?

Usage is implied rather than stated: you call this when you have a specific quote to commit and the person should pay themselves, and 'the agent never pays here' sets a boundary on the agent's role. There is no explicit when-not guidance or reference to an alternative tool for other booking/payment paths.

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