Skip to main content
Glama

Скрытые файлы сверх квоты

get_workspace_hidden_files
Read-onlyIdempotent

Возвращает число файлов, скрытых из-за нехватки места на диске, и стоимость их раскрытия. Сверх квоты файлы не удаляются, а скрываются — со стороны автора это выглядит как пропажа вложений в ответах. Оплату ассистент не проводит; апгрейд тарифа раскрывает файлы сам.

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

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 declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely non-obvious semantics beyond that: over-quota files are hidden rather than deleted, the symptom is missing attachments on the author's side, and the assistant must not take payment because a tariff upgrade reveals the files. It stops short of saying whether the returned cost is per-file or per-workspace, but the behavioral picture is strong.

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 sentences, front-loaded with what is returned before explaining the mechanism and the payment constraint. Each sentence carries information; only the mechanism sentence is slightly verbose, but it earns its place by explaining the confusing symptom.

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 read tool with no output schema, the definition covers what comes back (count and cost), why the files are absent, and what the agent must not do (pay). What is missing is only the shape of the returned cost value and any link to a sibling tool for a broader storage breakdown.

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?

There is a single required parameter, workspace_id, and schema coverage is 100% — the schema already explains it comes from workspace://list. The description adds nothing about the parameter, so the baseline of 3 for fully documented schemas 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 and resource: returns the count of files hidden due to insufficient disk space plus the cost to reveal them. It usefully corrects the likely inference from the name 'hidden_files' that a file list is returned, which separates it from manage_workspace_files. It does not name any sibling tool for comparison.

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 through the symptom it describes — attachments vanishing from responses on the author's side — rather than stated as an explicit trigger. It adds a real constraint ('Оплату ассистент не проводит; апгрейд тарифа раскрывает файлы сам') but gives no guidance on when to prefer this over get_workspace_storage_usage or get_workspace_storage.

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