Skip to main content
Glama

get_storage_usage

Read-onlyIdempotent

Obtiene el uso de almacenamiento del workspace: total de archivos subidos y espacio consumido.

Usar cuando el usuario pregunta cuánto espacio usa, si puede subir más archivos, o para auditar archivos del workspace.
Para ver los archivos individuales: usar get_all_files.

Retorna: total_files (cantidad), total_size_bytes, total_size_mb (redondeado a 2 decimales).

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": "get_storage_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by disclosing the concrete return fields and rounding behavior, which matters since there is no output schema. It does not mention any scope caveats (e.g., whether deletions/trash affect totals), which keeps it short of a 5.

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

Conciseness5/5

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

Three short blocks: what it does, when to use plus the alternative, and what it returns. Front-loaded with the purpose and zero filler sentences; every line carries 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 simple read-only aggregate with one optional parameter and no output schema, the description supplies purpose, routing to the sibling, and the exact return fields. An agent has everything needed to select and invoke it correctly.

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?

Only one optional parameter, and schema coverage is 100% — the schema already explains that workspace_id accepts a UUID or a user-spoken name and can be omitted when the token has a fixed workspace. The description adds nothing beyond that, so the baseline of 3 applies.

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 ('Obtiene el uso de almacenamiento del workspace') plus the exact contents (total files uploaded and space consumed). It also explicitly contrasts with the sibling get_all_files for per-file listings, so the agent can distinguish the two without opening schemas.

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?

Gives explicit when-to-use conditions: user asks how much space is used, whether more files can be uploaded, or wants to audit workspace files. It also names the alternative ('Para ver los archivos individuales: usar get_all_files'), which is complete routing guidance for this pair.

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