Skip to main content
Glama

Extend a stored object (paid, x402)

storage_renew

PAID: extend a stored file you own by another plan term; same id, contents untouched. 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_renew"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety triad (readOnly=false, destructive=false, openWorld=false), and the description adds substantial context beyond them: the unpaid call returns a price, payment goes in _meta['x402/payment'], and the accepted chains are listed. Existing contents are explicitly preserved, which is the key non-obvious behavior for an extend operation. Nothing contradicts the annotations.

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 operation and scope, then the payment mechanics and price floor — all useful. The 'Feedback: POST /feedback (free). Read daily; no individual reply.' sentence is unrelated to invoking this tool and dilutes focus.

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?

Covers the paid-call protocol, price source, and the no-mutation guarantee, which is what an agent needs to invoke correctly without an output schema. One gap: the schema marks both params optional (0 required) while the prose implies id is needed to identify the object, and that discrepancy is never reconciled.

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 coverage is 100% and both parameters are already documented, including the enum and the note that plan sets size limit and price. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 specific verb and resource ('extend a stored file you own by another plan term') plus a differentiating scope note ('same id, contents untouched'), which separates it from replacement-style siblings. It stops short of naming storage_replace or storage_buy explicitly, so the agent must infer the contrast.

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?

Clear context: use this when the object already exists and is owned; the 'you own' qualifier implicitly routes new purchases elsewhere. The two-step unpaid-then-pay flow is spelled out, but no explicit when-not or named alternative is given.

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