Skip to main content
Glama

Re-fetch a venue and diff it against our baseline (paid, x402)

drift_check

PAID: detect API drift: we re-fetch a venue we snapshot and diff it against our baseline (fields added, removed, moved). Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0100 USDC.

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

Input Schema

NameRequiredDescriptionDefault
venueNoA venue id we hold a baseline snapshot for; list them free with drift_venues. A venue we have never snapshotted is refused (404).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "venue"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / venue / description
      Previous value: -"A venue id we hold a baseline snapshot for; list them free with drift_venues. A venue we have never snapshotted is a free 404, never a charge."New value: +"A venue id we hold a baseline snapshot for; list them free with drift_venues. A venue we have never snapshotted is refused (404)."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the safety flags; the description adds the entire payment model, the accepted chains and currency (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei, X Layer), the exact price, and the retry-after-payment protocol. readOnlyHint=false is consistent with funds movement via x402 rather than contradicting the read-like diff.

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?

Front-loads 'PAID: detect API drift' and the diff semantics, then compression-packs payment, price, and feedback into short clauses with no filler. Every sentence carries operational information.

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 single-parameter paid tool with no output schema, it covers cost, payment flow, refusal behavior, and the nature of the returned diff. The one gap is the concrete shape of the diff payload, which an agent must discover empirically. Otherwise an agent can call this correctly from the description alone.

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?

Only one parameter and schema coverage is 100%, so the schema already documents `venue`, including the free listing tool and the 404-on-unknown-venue behavior. The description reinforces that the venue must be one already snapshotted but adds no format details beyond that. 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?

States a specific verb and resource: re-fetch a snapshotted venue and diff it against a baseline, naming the diff units (fields added, removed, moved). This is clearly distinct from generic fetch tools like check_url or scrape_page. It stops short of naming a sibling alternative to route away from, but the operation is unambiguous.

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?

Gives concrete invocation guidance: an unpaid call returns the price, then pay via _meta['x402/payment'] and call again. It also states the read cadence ('Read daily') and that feedback goes through a separate free endpoint. No explicit when-not-to-use case is given, which keeps it from a 5.

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