Skip to main content
Glama

track_confirmation

Converts any merchant booking confirmation into a portable record plus an ICS calendar invite, accepting pasted text or structured JSON from restaurant, hotel, flight, or order artifacts.

Instructions

Normalize any merchant confirmation into a portable record plus an ICS calendar invite. Feed it the artifact any booking tool returned. Costs $0.005 per call, paid in USDC over x402 to x402-confirmations. Returns the merchant's artifact and the payment receipt.

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

Input Schema

NameRequiredDescriptionDefault
railNoPayment rail for this call. Overrides the configured default (auto). auto = whichever rail this agent holds a key for.
typeNorestaurant | hotel | order | flight | appointment | generic
rawTextNoFreeform confirmation text, e.g. a pasted email
confirmationNoStructured confirmation JSON from a merchant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / confirmation / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does so well on the commercially important traits: a stated price ($0.005 per call), a stated payment mechanism (USDC over x402 to x402-confirmations), and stated returns. It omits failure semantics — whether the fee is charged on error, retry/idempotency behavior, and whether the normalized record persists anywhere — which keeps it from a 5 for an unannotated, paid operation.

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?

Four short sentences in a deliberate order: what it does, what to give it, what it costs, what comes back. No filler, no repetition of schema content, and the core purpose is front-loaded.

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?

There is no output schema, so the description correctly compensates by enumerating returns (portable record, ICS invite, merchant artifact, payment receipt). Cost and payment rail are covered. What remains thin is error/timeout behavior for a paid network call, which matters given the per-call charge.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema doesn't: the opaque 'confirmation' object and 'rawText' accept whatever artifact any booking tool emitted, and 'normalize any merchant confirmation' signals broad, shape-agnostic acceptance rather than a fixed contract. The 'rail' parameter's connection to the x402/USDC payment is only implied, not spelled out.

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 — 'Normalize any merchant confirmation' — and names the concrete outputs: a portable record plus an ICS calendar invite. That output signature is unlike anything in the sibling set (book_table, search_flights, spending_report), so an agent can place it as a post-booking normalization step without ambiguity.

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?

'Feed it the artifact any booking tool returned' gives explicit context for when to call it: after some other tool has produced a confirmation. It does not state exclusions (e.g., don't call before a booking exists) or name any alternative, so it stops short of the full when/when-not bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.