Skip to main content
Glama

Новая папка

create_folder

Создает новую папку для группировки опросов в выбранном workspace.

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": "<name>"
    },
    "name": "create_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoЗначок папки в кабинете. Не передан или null — обычная папка.
nameYesНазвание папки (до 100 символов, без ссылок).
colorNoЦвет папки в кабинете. Не передан или null — серый.
workspace_idYesID workspace. Взять из workspace://list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / color
      Added value: +{
      +  "description": "Цвет папки в кабинете. Не передан или null — серый.",
      +  "enum": [
      +    "blue",
      +    "violet",
      +    "pink",
      +    "red",
      +    "orange",
      +    "yellow",
      +    "green",
      +    "teal",
      +    null
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / icon
      Added value: +{
      +  "description": "Значок папки в кабинете. Не передан или null — обычная папка.",
      +  "enum": [
      +    "star",
      +    "heart",
      +    "flag",
      +    "bookmark",
      +    "briefcase",
      +    "users",
      +    "chart",
      +    "target",
      +    "megaphone",
      +    "chat",
      +    "cart",
      +    "gift",
      +    "book",
      +    "graduation",
      +    "lightbulb",
      +    "rocket",
      +    "globe",
      +    "calendar",
      +    "zap",
      +    null
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Название папки (max 255 символов)."New value: +"Название папки (до 100 символов, без ссылок)."
    • addedInput schema / properties / name / maxLength
      Added value: +100
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the mutation-but-safe-creation profile is covered. The description adds only the organizational intent of the created folder and says nothing beyond annotations — no note on whether a duplicate name is rejected, whether a folder count limit applies, or what identifier is returned for later use.

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 front-loaded sentence with zero filler, correct verb first and purpose last. It is efficiently sized, though the brevity is partly under-specification rather than deliberate compression.

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

Completeness3/5

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

For a simple 4-parameter creation tool with full schema coverage, no output schema and complete annotations, the description is minimally sufficient to pick the tool. It still leaves the agent without the returned folder identifier and without any guidance on repeat creation or uniqueness, which matters for a non-idempotent create call.

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 schema already documents name length limit, the icon and color enums, and the default gray/plain-folder fallback when null is passed. The description restates none of these and adds no meaning beyond the schema, 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?

The description names a specific verb (Создает) and resource (новую папку) and adds the business purpose — grouping surveys inside a chosen workspace. It is clearly distinguishable from read-oriented siblings like get_folder_list, but it never contrasts itself with the adjacent manage_workspace_folder or manage_folder_access tools.

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 explicit when-to-use or when-not-to-use guidance and no mention of alternatives; the agent is left to infer that this is the creation path versus the manage/get folder tools. The only implicit cue is 'в выбранном workspace', which hints a workspace must be chosen first (the schema's workspace://list reference is what actually tells the agent how).

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