Skip to main content
Glama

Store an object (paid, x402)

storage_buy

PAID: store a file (bytes as base64) for the plan term; the paying wallet owns it. Returns its id and expiry. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: from $0.0100 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "storage_buy"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoStorage plan; it sets both the size limit and the price. See GET /pricing or the service_card tool for the live table.
labelNoOptional caller-chosen label, up to 256 characters, no control characters.
contentBase64NoThe bytes to store, base64-encoded. Decoded size must fit the plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "plan",
      -  "contentBase64"
      -]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), it discloses that the call is paid, the accepted chains and currency (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei, X Layer), the two-phase unpaid/paid flow, ownership by the paying wallet, and that it returns id and expiry. The trailing 'Feedback: POST /feedback (free). Read daily; no individual reply.' is boilerplate that muddies rather than clarifies behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The paid/price/payment information is front-loaded and dense, which is good, but the feedback-endpoint sentence and 'Read daily; no individual reply' are unrelated to storing an object and consume attention without earning their place.

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

Completeness4/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 correctly covers the return values (id and expiry) and the payment handshake, which are the parts an agent most needs. It leaves open what happens at plan expiry, how size limits map to plans (deferred to GET /pricing or service_card), and why zero parameters are formally required.

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 description coverage is 100%, so the schema already documents plan, label and contentBase64 in detail, making 3 the baseline. The description adds only 'for the plan term' and the paying-wallet ownership notion; it does not clarify that plan and contentBase64 are effectively required despite the empty required list.

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 names a specific verb and resource ('store a file (bytes as base64)') and adds distinguishing scope: storage is for the plan term and owned by the paying wallet, which separates it from the renew/replace siblings. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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 concrete invocation path: call unpaid to learn the price, then pay via x402 in _meta['x402/payment'] and call again. What is missing is guidance on when to choose this over storage_renew or storage_replace, and no exclusions are stated.

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