Skip to main content
Glama

Список папок

get_folder_list
Read-onlyIdempotent

Возвращает список папок текущего пользователя.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idNoID аккаунта из workspace://list: только папки этого аккаунта. Без него — папки всех аккаунтов, к которым есть доступ, — и своих, и тех, куда вас пригласили.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace_id
      Added value: +{
      +  "description": "ID аккаунта из workspace://list: только папки этого аккаунта. Без него — папки всех аккаунтов, к которым есть доступ, — и своих, и тех, куда вас пригласили.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

C2.6/5.0
Behavior2/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 the safety profile is fully covered by structured data. The description adds only a scope phrase that is arguably narrower than the actual behavior (all accessible accounts), and says nothing about ordering, pagination, or what a folder entry contains.

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 short sentence with no filler, and the scope qualifier is front-loaded. It is efficient but border-line under-specified rather than verbose; nothing wasteful, but also nothing extra that earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one optional parameter, no output schema, straightforward annotations), so the bar is low, yet the description still omits the multi-account behavior that is the main subtlety of this call. An agent reading only the description would not know the unparameterized call spans invited accounts.

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% and the single workspace_id parameter is thoroughly documented in the schema, including referencing workspace://list and the all-accounts default. The description mentions the parameter not at all, so baseline 3 applies, with a slight negative for implying a narrower result set than the schema documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb and resource ('Возвращает список папок') with a scope qualifier ('текущего пользователя'). However, that scope contradicts the schema: without workspace_id the tool returns folders from all accessible accounts, including invited ones, so an agent could misjudge what it will receive. It also does not distinguish itself from siblings such as create_folder or manage_folder_access.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no named alternative for folder-related tasks. The only routing logic present ('текущего пользователя') lives in the schema, not the description, so the description offers nothing about choosing this tool over create_folder or get_workspace_list.

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