Skip to main content
Glama

Purchase one wellness music track

purchase_track

Purchase a single track ($5.99 USDC via x402 v2 or v1). Returns the stream URL and x402 payment requirements; GET the URL with a PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) header to receive the MP3 and an X-LGDA-Session token, then POST telemetry to /verify-session for a signed receipt.

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": {
      "track_id": "<track_id>",
      "session_id": "<session_id>"
    },
    "name": "purchase_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNo
track_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 disclose meaningful behavior: the exact cost, the two protocol versions and their distinct header names, the returned stream URL plus payment requirements, and the session token issued on success. It stops short of covering failure modes (insufficient payment, expired session) or idempotency of repeated purchases.

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?

A single dense sentence that front-loads the action and price before the workflow details, with zero filler. It is somewhat run-on and would scan better as a short ordered list of steps, but every clause carries information.

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?

The multi-step payment flow is well covered for a tool with no output schema and no annotations, but the definition leaves key gaps for an agent: the semantics of the three parameters and what to do when payment or verification fails. Adequate, not complete, for a paid workflow tool.

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: track_id is only obliquely implied, and session_id and agent_id are never explained (is session_id pre-existing or the one returned? is agent_id optional?). The pattern and length constraints live only in the schema, uninterpreted.

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 ("Purchase a single track"), adds price and protocol ($5.99 USDC via x402 v2 or v1), and is plainly distinguishable from the sibling purchase_album. An agent can tell what this does without opening the schema.

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?

Gives a clear downstream procedure (GET the returned URL with a payment header, then POST telemetry to /verify-session), which implicitly tells the agent how to use the result. However, it never states when to choose this over purchase_album or list_catalog, nor any prerequisites for holding a valid session_id.

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.