Skip to main content
Glama

models

Download model (x402 paid)

download_model

x402-gated download access, $0.10. Call without payment to get the offer (accepts: Base USDC via EIP-3009 gasless, or legacy on-chain USDC/USDT/PYUSD on Solana/Tron/EVM). Then retry with payment.payload (base64 PaymentPayload) or payment.tx_hash + payment.network. Returns access_token + download URL.

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": {
      "model_id": "<model_id>"
    },
    "name": "download_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentNoPayment proof from the offer
model_idYes8-char hex model id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false, so the description carries most of the burden and does well: it discloses the price, the accepted payment rails and schemes (EIP-3009 gasless on Base, legacy on-chain USDC/USDT/PYUSD on Solana/Tron/EVM), and the return values. It stops short of stating failure behavior, whether a payment is consumed on error, or expiry of the offer/token, which are the remaining behavioral gaps for a paid mutation.

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?

Three compact sentences, front-loaded with the gate and price, then the call sequence, then the return. Dense with parenthetical payment-rail detail that is useful but slightly crowds the core instruction; no sentence is filler.

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 must state returns and it does (access_token + download URL). Combined with the price, the two payment branches, and the model_id requirement, an agent has everything needed to complete the call flow.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that omitting `payment` is a legitimate first call, and that tx_hash must be paired with network while payload is the base64 alternative. That conditional/pairing logic is not obvious from the flat nested schema alone.

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 ('download access') plus the distinguishing trait that it is x402-gated and costs $0.10, which separates it from the read-only siblings get_model_card and search_models. An agent can tell immediately that this is the paid retrieval step, not a metadata lookup.

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 an explicit two-stage protocol: call without `payment` to obtain the offer, then retry with either payment.payload or payment.tx_hash + payment.network. The conditions selecting each payment path are named, leaving nothing to inference about sequencing.

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