Skip to main content
Glama

Orbit Channel

Buy a track

purchase_music

Buy permanent access to one track. Spends the user's Orbit credits and cannot be undone, so confirm with the user first. Needs an authorized session (authorize_with_code); without one it returns authorization.required.

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": {
      "articleId": "<articleId>"
    },
    "name": "purchase_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
articleIdYesArticle ID of the music to purchase.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call did not succeed.
successNo
displayCardNoMarkdown to show to the user.
authorizationNoPresent when the session must be authorized first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the critical consequences: it spends Orbit credits, cannot be undone, requires user confirmation, and fails without authorization. These are exactly the behavioral facts an agent needs before invoking an irreversible purchase. The description does not contradict the non-read-only, non-idempotent annotations.

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?

The definition is three short sentences and front-loads the core purchase action. The follow-up sentences add essential warnings about credit spend, irreversibility, confirmation, and authorization. Nothing is redundant.

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?

For a simple one-parameter purchase tool with an output schema, the description covers the important gaps: cost, irreversibility, user confirmation, and auth failure. No return-value explanation is needed because an output schema exists. The description is complete enough for correct invocation.

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?

There is only one parameter, articleId, and schema description coverage is 100%, with the schema already explaining it as the Article ID of the music to purchase. The description adds "one track" but no further syntax, source, or constraints. With the schema doing the parameter work, the 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?

The description states a specific verb and resource: "Buy permanent access to one track." It distinguishes a permanent purchase from nearby actions like searching or temporary streaming. An agent can identify the operation 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 Guidelines4/5

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

It gives clear preconditions: confirm with the user first and use an authorized session via authorize_with_code. It also names the authorization.required error when unauthenticated. It does not explicitly compare against alternatives such as request_stream_access, but the usage context is clear.

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