Tokenrip

Show storage usage

storage_usage

Read-onlyIdempotent

Read storage usage for your account, or a team you belong to (team): the plan, bytes used and the limit (null: no limit), bytes per workspace, standalone and bundle bytes, trashBytes (the part of usedBytes in the trash), and the largest artifacts with their current and history bytes. Every kept version, table row and bundle version counts, and so does the trash until it is purged. A workspace counts toward its owner. A platform admin reads any team, or another account with account (an account id or alias; anyone else: FORBIDDEN).

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_usage"
  }
}

Input Schema

Name	Required	Description	Default
`team`	No	A team's storage, by slug or id (members only; a platform admin reads any team's).
`account`	No	Another account's storage, by account id or alias (platform admins only; anyone else is refused FORBIDDEN). Not with team.

Output Schema

Name	Required	Description	Default
`plan`	Yes
`payer`	Yes
`largest`	Yes
`usedBytes`	Yes
`limitBytes`	Yes
`trashBytes`	Yes
`workspaces`	Yes
`bundleBytes`	Yes
`standaloneBytes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / properties / plan / enum

Previous value: -[
-  "free",
-  "pro",
-  "team",
-  "enterprise"
-]New value: +[
+  "free",
+  "pro",
+  "power",
+  "enterprise"
+]

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive, so the description focuses on non-obvious semantics: null limit means no limit, trash counts until purged, every kept version/table row/bundle version counts, and a workspace bills to its owner. It does not mention freshness/latency of the numbers, which is the one thing an agent might still wonder about.

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 scope are front-loaded in the first clause, and the access rules come last where they belong. The middle inventory of returned fields (trashBytes, standalone/bundle bytes, largest artifacts) is somewhat dense and overlaps the output schema, so it is not maximally tight.

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 two-param read tool with a full output schema and complete annotations, this covers everything needed to call it: who may pass which parameter, what happens on refusal, and how usage is accounted. The enumeration of return fields is arguably redundant given the output schema, but nothing required is missing.

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 documented there, so the schema already carries the load. The description restates the same access rules (members-only team, admin-only account, "not with team") rather than adding syntax, format, or default behavior beyond the schema.

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?

Opens with a specific verb+resource ("Read storage usage") and immediately bounds the scope: own account, a team, or (for admins) another account. The enumeration of what the read returns (plan, bytes used, limit, per-workspace, trashBytes, largest artifacts) makes it unmistakable against siblings like workspace_show or team_show.

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?

Gives explicit selection conditions for both modes — team by slug/id for members, account for platform admins — plus the exclusion "anyone else: FORBIDDEN" and the implicit mutual exclusivity with team. No sibling alternative is named, but no sibling offers storage usage, so there is nothing to route away from.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tokenrip tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.