Skip to main content
Glama

PlaceProfile evidence: venue atmosphere, verified (paid)

The tracks behind a venue's atmosphere, with a Bitcoin receipt

get_venue_tracks
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. The recordings behind a venue's atmosphere: every track in its published playlist with its twelve audio features, ISRC and artist, the published record's SHA-256, and a receipt of this read 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

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": {
      "slug": "<slug>"
    },
    "name": "get_venue_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe venue's slug, as find_venues and get_venue return it (the last part of its profile_url).
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.1/5.0
Behavior5/5

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

The annotations only say readOnly/openWorld/not-idempotent, so the payment mechanics are entirely the description's burden and it carries them: the first reply is a price quote, nothing is charged until the agent signs, and the read is anchored in Bitcoin and bound to the payment. It also discloses the free jsonld escape hatch and that the declared figure is what drives the price band, which an agent needs before calling.

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-loaded with the most decision-relevant fact ("PAID, from one cent in USDC by x402") and organized as price, payload, audience, free alternative, sibling exclusion. Dense but nearly every clause earns its place; the payment sentences could be tightened slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description enumerates the return payload (tracks, twelve audio features, ISRC, artist, SHA-256, receipt) so the agent knows what comes back. It also covers the paid flow and the free alternative, which is everything needed to call this correctly given openWorldHint.

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 coverage is 100%, so slug, purpose, reference and declaredValueUsd (including the one-cent/ten-cent/one-dollar bands) are already documented in the schema. The description adds only that purpose and reference are bound into the anchored receipt, which the schema also states. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description states a specific resource and its contents: "every track in its published playlist with its twelve audio features, ISRC and artist" plus a SHA-256 and Bitcoin-anchored receipt. That is concrete enough for an agent to know what it returns, and it explicitly distinguishes itself from find_venues ("Not a search: find_venues finds places, free"). It stops short of a crisp verb framing and never contrasts with get_venue or verify_venue.

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 a usage context ("For an AI agent that books, places or reports on a venue by its atmosphere and must later show what it checked") and a when-not with a free alternative ("The venue's record itself is free to read at its profile_url + '.jsonld'"). The exclusion against find_venues is explicit. What is missing is guidance on when this is preferable to the sibling get_venue, which is the more likely confusion.

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