Skip to main content
Glama

Set registry storage addon

set_registry_storage_addon
Destructive

Buy or return paid registry storage: set how many storage blocks the organisation holds (blocks is the new total, not a difference). Each block adds block_gib GiB (50 GiB) to the limit of every registry project and is billed on the monthly invoice at the block price (EUR 5 a month), prorated by the days held. Read get_registry_storage first: addon.blocks is what is held, addon.max_blocks is the most that can be bought here (for more, use request_limit_increase with kind registry_storage), addon.billing_ready and addon.billing_blocker say whether billing can pay, and addon.version goes back as expected_version - if the storage or its price changed since, the call is refused ("Registry storage changed since you read it"): read again and confirm the new price, never retry the same arguments. Reducing is always possible, but never below what the registry already holds (the refusal names the minimum). Pass current_blocks, price_cents_per_block_month and block_gib from the read so the confirmation names the monthly price change (blocks x price); they are checked against the live add-on and a mismatch is refused. The new limit is applied to the registry at once. Requires billing.manage.

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": {
      "blocks": "<blocks>",
      "current_blocks": "<current_blocks>",
      "price_cents_per_block_month": "<price_cents_per_block_month>",
      "block_gib": "<block_gib>"
    },
    "name": "set_registry_storage_addon"
  }
}

Input Schema

NameRequiredDescriptionDefault
blocksYesThe number of storage blocks the organisation should hold after the change (0 returns them all).
block_gibYesaddon.block_gib from the read: the size of one block in GiB (50). The confirmation shows it, and the call is refused if the block size is no longer this.
current_blocksYesaddon.blocks from the read: the blocks held now. The confirmation shows the change from it, and the call is refused if it is no longer true.
expected_versionNoAlways send the addon.version get_registry_storage returned: if the blocks or the price changed since, the change is refused instead of buying at a price nobody confirmed. Omit it only when that read returned no version.
price_cents_per_block_monthYesaddon.price_cents_per_block_month from the read: what one block costs this organisation per month, in cents. The confirmation shows the monthly price from it, and the call is refused if the price is no longer this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses pricing mechanics (EUR 5/block/month, prorated by days held), that the new limit is applied to the registry at once, the required billing.manage scope, and the optimistic-concurrency contract via expected_version with the exact refusal message. This goes well past what readOnly/destructive hints convey.

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?

Purpose and the read-first precondition are front-loaded, then billing, then the concurrency rule. It is a dense single paragraph with mild repetition ('blocks is the new total, not a difference' also appears in the schema), but nearly every clause carries actionable information.

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 five-parameter mutating billing tool with no output schema, the definition covers what the call does, what must be read beforehand, what gets refused and why, and what the user sees in the confirmation. Nothing needed to invoke it correctly is missing.

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 would be 3, but the description adds the rationale the schema does not: current_blocks, price_cents_per_block_month and block_gib are sent only so the confirmation can name the monthly price change and so stale reads are refused. The expected_version round-trip ('addon.version goes back as expected_version') is also spelled out as a workflow, not just a field.

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 ('Buy or return paid registry storage: set how many storage blocks the organisation holds') and immediately scopes the semantics ('blocks is the new total, not a difference'). It also names the two siblings it must be distinguished from (get_registry_storage for reading, request_limit_increase for going beyond max_blocks).

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?

Explicitly says to read get_registry_storage first and which fields to take from that read, names request_limit_increase as the alternative when max_blocks is exceeded, and gives a concrete when-not rule: on a 'Registry storage changed since you read it' refusal, re-read and confirm the new price, never retry the same arguments. Reduction constraints are also 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.