Skip to main content
Glama

Venue atmosphere verification, Bitcoin timestamp (PlaceProfile, paid)

Verify a venue's measured atmosphere, with a Bitcoin receipt

verify_venue
Read-only

PAID, from one cent in USDC by x402; the first reply is the price and nothing is charged until the AI agent signs a payment. Proof of a venue's measured atmosphere: the venue-level averages (energy, loudness, tempo, acousticness, danceability and the rest) recomputed from the audio features of every track in its published playlist, each track's record checked against its hash, the published record exactly as it was read with its SHA-256, and a receipt of this check anchored in Bitcoin and bound to the payment. For an AI agent that books, places or reports on a venue by its atmosphere and must later show what it checked. The venue's record itself is free to read at its profile_url + '.jsonld'. Not a search: find_venues finds places, free.

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

Input Schema

NameRequiredDescriptionDefault
slugNoThe venue's slug, as find_venues and get_venue return it (the last part of its profile_url).
slugsNoSeveral venues in one call, in place of slug: one payment and one receipt for all of them.
purposeNoOptional: what the AI agent is about to do, in its own words, such as booking the venue for an event. Bound into the anchored receipt as part of the call.
referenceNoOptional: the AI agent's own reference for the action, such as a booking id or sha256:<hash> of its document. Bound into the anchored receipt as part of the call.
declaredValueUsdNoThe stakes in US dollars the AI agent is acting on, such as the value of a booking or a placement. They set the price band (one cent under $100, ten cents from $100, one dollar from $10,000); undeclared stakes are priced at one cent. The declared figure is part of the call that the receipt anchors in Bitcoin, so the receipt shows it. No money other than the price moves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/not-idempotent, and the description adds the commercially important behavior on top: it is paid via x402, the first reply is only a price quote, and nothing is charged until the agent signs a payment, with price bands set by declaredValueUsd. It does not explain the mechanics of the follow-up signed call or what the eventual response payload looks like. "PAID" alongside readOnlyHint=true is not a contradiction, since readOnly concerns data mutation, not billing.

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?

Front-loads the decisive fact ("PAID, from one cent in USDC by x402") and then layers proof contents, audience, free alternative, and sibling differentiation. It is dense and run-on, packing many clauses into long sentences, but almost every clause carries information an agent needs.

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 five-parameter paid tool with no output schema, the description covers cost model, what is proven, receipt anchoring, and the free alternative. The gap is the interaction flow after the price quote: how the payment is signed and what the agent receives on success is left implicit.

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 the schema already documents slug, slugs, purpose, reference, and declaredValueUsd. The description reinforces the pricing role of declaredValueUsd and the receipt-binding of purpose/reference, but adds little semantics the schema does not already carry. Baseline 3 applies.

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 (verify) and a specific object (a venue's measured atmosphere), then enumerates exactly what the verification covers: recomputed venue-level audio averages, per-track hash checks, the source record with its SHA-256, and a Bitcoin-anchored receipt. It explicitly separates itself from the search sibling with "Not a search: find_venues finds places, free."

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

Usage Guidelines5/5

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

Gives a concrete use case ("an AI agent that books, places or reports on a venue by its atmosphere and must later show what it checked") and two explicit escape hatches: the raw record is free at profile_url + '.jsonld', and find_venues is the tool for locating places. That is when-to-use plus when-not-to-use plus a named alternative.

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