Skip to main content
Glama

Занятое место

get_workspace_storage_usage
Read-onlyIdempotent

Возвращает занятое файлами место: отдельно диск платформы (он идёт в квоту тарифа) и своё хранилище. Для своего S3 объём считается обходом бакета, для Яндекс.Диска дополнительно показывается остаток места аккаунта.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_workspace_storage_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add real behavioral value — and it does: S3 volume is obtained by traversing the bucket (implying a potentially slow/expensive call), while Yandex.Disk additionally reports the account's remaining space. It does not mention caching, cost, or units, 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.

Conciseness4/5

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

Two tight sentences, front-loaded with what is returned, with the storage-backend caveats following. No filler; the only small inefficiency is that the backend-specific behavior is compressed into one dense clause.

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?

With no output schema, the description carries the burden of describing the return payload and does so at a useful level: two separate figures plus an extra remaining-space value for Yandex.Disk. For a single-parameter read-only tool that is largely sufficient, missing only units and field-level detail.

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 parameter, and the schema already documents it fully (100% coverage, including the workspace://list provenance hint). The description adds no further meaning about workspace_id, 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+resource: returns space occupied by files, broken into platform disk (which counts against the tariff quota) and own storage. An agent can tell this is the usage-reporting tool rather than a storage-configuration one, though it never names the nearby get_workspace_storage / verify_workspace_storage tools to sharpen the distinction.

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 content of the answer (quota consumption, remaining account space), so an agent can infer when to reach for it. There is no explicit when-to-use/when-not-to-use statement and no routing to or from the sibling storage tools.

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