Skip to main content
Glama

Replace a stored object (paid, x402)

storage_replace
Destructive

PAID: replace the contents of a stored file you own, keeping its id, with a fresh plan term. 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_replace"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe object id returned when it was bought.
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 replacement bytes, 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: -[
      -  "id",
      -  "plan",
      -  "contentBase64"
      -]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds real context on top: ownership requirement, id preservation, accepted chains and payment field, minimum price, and the free feedback endpoint. It stops short of saying whether the prior bytes are recoverable, which matters for a destructive replace.

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?

Front-loaded with the paid, destructive action and then the payment mechanics, so the critical facts come first. The feedback and read-cadence sentence is service-wide boilerplate that dilutes focus slightly but is short.

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?

For a destructive, paid mutation with no output schema, the description covers payment mechanics, currency options, price entry point, and id semantics. Missing only edge behavior, such as what happens when replacement bytes exceed the selected plan.

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 all four params are already documented, including the plan enum and its pricing pointer. The description only reinforces that id is retained and that plan drives both size limit and price, which is baseline value, not new meaning.

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?

States a precise verb and resource: replace the contents of a stored file you own while keeping its id. That clearly separates it from creating or renewing in spirit, though it never names storage_buy or storage_renew to make the distinction explicit.

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 explains the paid call flow well (an unpaid call returns the price, then you pay via x402 in _meta['x402/payment'] and retry), which is genuine usage guidance. It does not say when to prefer this over storage_renew or storage_buy, so alternatives remain implied.

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