Skip to main content
Glama

Своё хранилище файлов

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

Input Schema

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

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, idempotentHint and destructiveHint=false, so the safety profile is largely covered; the description usefully reinforces it by stating that storage cannot be changed from here. It adds the diagnostic framing (запись ушла на диск платформы) but no auth, rate-limit or latency context beyond that.

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?

Three short sentences ordered by value: what is returned, what is prohibited, when to reach for it. No filler, though the return-field enumeration is dense enough that it could be listified for faster scanning.

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 compensates by enumerating the returned fields (type, health, path template, file count), and annotations cover the safety profile. It leaves unclear how the file count differs from get_workspace_storage_usage, which is the only material gap.

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 description coverage is 100% for the single workspace_id parameter and points at workspace://list, so the schema already carries the meaning. The description adds nothing about the parameter; 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?

Specific verb ('Возвращает') plus a precisely enumerated resource: connection type (S3 или Яндекс.Диск), health, path template, file count. An agent knows exactly what it will get back, though it does not name the close sibling get_workspace_storage_usage, which also reports storage-related data.

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 a concrete diagnostic trigger ('Нужен, когда файлы ответов не открываются') and rules out a class of actions by stating that connecting/disconnecting is done in the UI, not via the assistant. It stops short of naming an alternative tool to call instead when the problem is usage or verification.

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