Skip to main content
Glama

ExducerAI GPU cloud

Object storage usage

get_storage_usage
Read-onlyIdempotent

Object storage: GB stored, active keys, price per GB-month and the amount billed this month (not available to a sandbox key).

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 safety is covered. The description adds genuinely useful context beyond that: the returned metrics and the sandbox-key restriction. It does not cover caching or freshness of the figures, so it is additive but not rich.

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?

A single tight sentence, front-loaded with the resource and then the metric list; the access caveat is appended where it belongs. Nothing is padded, though a leading verb would make it scan even faster.

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 zero-parameter read tool with no output schema, the description does the essential work of telling the agent what the response contains and one access limitation. The absence of an output schema means exact field names and formatting remain unstated, which is a minor residual gap.

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?

There are zero parameters, so there is nothing to disambiguate; the description instead defines the semantics of the returned fields (GB stored vs. price per GB-month vs. billed amount). Baseline for a no-param tool applies, with the field definitions as a small bonus.

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 resource (object storage usage) and enumerates exactly what is returned: GB stored, active keys, price per GB-month, and amount billed this month. This distinguishes it from get_billing (invoices) and get_usage, though it does not name those siblings explicitly.

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?

Usage is implied by the data it returns (checking storage consumption and cost), and the parenthetical flags one exclusion — sandbox keys cannot use it. It does not explicitly say when to prefer get_usage or get_billing instead, leaving routing to inference.

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