Skip to main content
Glama

Purchase a wellness music album (3 tracks)

purchase_album

Purchase a whole album ($14.99 USDC via x402 v2 or v1). One payment entitles the buyer to all 3 tracks on the album. Returns stream URLs and x402 payment requirements; pay once, then present the issued X-LGDA-Session token to /stream for each track.

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": {
      "album_id": "<album_id>",
      "session_id": "<session_id>"
    },
    "name": "purchase_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNo
album_idYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 burden and does well: it discloses the exact price ($14.99 USDC), the accepted payment protocols (x402 v2 or v1), that a single payment entitles the buyer to all three tracks, and the session-token mechanic for subsequent streaming. It stops short of covering failure/refund behavior, whether entitlement is bound to session_id, or whether repeat purchases are idempotent.

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?

Two sentences, front-loaded with the price and scope, then the payment/streaming mechanics. Dense but every clause carries information; slightly terse for the amount of mechanism it compresses.

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?

For a paid mutation tool with no annotations and no output schema, the description usefully explains what comes back (stream URLs, x402 payment requirements). But it leaves the optional agent_id undefined and says nothing about payment failure, duplicate charges, or what happens if the session token is missing — significant gaps for a money-spending operation.

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 three parameters, so the description must compensate and largely does not. "album_id" and "session_id" are only inferable indirectly, and the optional "agent_id" is never mentioned at all; the phrase "issued X-LGDA-Session token" even risks confusing the returned token with the session_id input.

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?

"Purchase a whole album" is a specific verb and resource, and the follow-up sentence ("all 3 tracks on the album", "pay once") makes the album-wide scope explicit, which is exactly what separates it from a single-track purchase.

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?

The description gives a clear post-purchase workflow (pay once, then present the issued X-LGDA-Session token to /stream per track), which is real usage context. However, it never states when to choose an album purchase over a track purchase, nor any exclusions or prerequisites for the buyer.

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.