Skip to main content
Glama

Проверка своего хранилища

verify_workspace_storage

Проверяет связь с подключённым хранилищем: пробует записать и прочитать пробный файл. Удачная проверка возвращает запись новых файлов в своё хранилище, если оно раньше отвалилось и запись временно шла на диск платформы. Запускать может только владелец аккаунта.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description usefully explains the side effects behind readOnlyHint=false: the call actually creates and reads a test file, and a successful check re-routes new file writes back to the workspace storage. It also adds the owner-only auth requirement. It does not explain why the operation is non-idempotent (each call writes another probe file), which is the one annotation left unelaborated.

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, front-loaded with the mechanism, followed by the effect and the permission constraint — no filler. The middle sentence ('Удачная проверка возвращает запись новых файлов...') is slightly ambiguous between a returned value and a state change, which costs it a point.

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 one-parameter tool with no output schema, the description covers mechanism, side effects, and access restriction adequately. The only soft spot is the unclear phrasing about what a successful check actually returns versus changes, which an agent might misread when reporting results.

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, including its source (workspace://list), so the schema does the work. The description only implies scope via 'своего хранилища' and adds no format or selection detail beyond the schema.

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?

The description gives a specific verb and mechanism: it checks the connection to the connected storage by writing and reading a probe file. That distinguishes it from plain info tools like get_workspace_storage, but it never names a sibling or explicitly contrasts itself with them.

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?

It states a clear usage context — run it when storage previously dropped and writes were temporarily landing on the platform disk — and adds the prerequisite that only the account owner can invoke it. It does not explicitly say when NOT to use it or point to get_workspace_storage as the read-only alternative.

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