Skip to main content
Glama
Sign In

ThreadPage

by page.thread
OverviewDiscussionsAdmin

Create a folder

create_folder
Idempotent

Create a Folder to group Threads. Folders are optional: create one only when the person asks or their Folders clearly call for it, then put Threads in it with move_thread or create_thread. parent_id: a Folder's id from list_folders, or null for the top level (needs whole-workspace access); a live sibling with the same name answers folder_name_conflict. Needs Can edit and organize. Answers a receipt with the new Folder's id (entity_id), revision and url; the same operation_id answers it again instead of creating a second Folder.

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

Input Schema

NameRequiredDescriptionDefault
nameYes1–200 characters.
parent_idNoThe parent Folder's id, or null for the top level.
operation_idYesA new UUID for each write. After a lost answer, send the identical call with the same one, or check get_operation before writing again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the annotations: it names the required permission ('Can edit and organize'), the specific failure mode ('a live sibling with the same name answers folder_name_conflict'), the return payload shape (entity_id, revision, url), and how idempotency resolves a lost answer. The only gap is that it doesn't say whether the name is trimmed or otherwise normalized.

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?

Front-loaded with purpose and the optionality rule, then compact field notes; nearly every clause carries distinct information. The 'parent_id:' colon-style fragment is slightly telegraphic, but nothing is redundant.

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

Completeness5/5

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

No output schema exists, yet the description explains the receipt contents (entity_id, revision, url) and the idempotent replay behavior. Combined with permission and conflict disclosure, an agent has everything it needs to call this mutation safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning the schema lacks: parent_id must be a Folder id from list_folders, and null implies whole-workspace access, and it explains the sibling-name conflict consequence. That is real semantic enrichment rather than restatement.

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

Purpose5/5

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

Opens with a specific verb+resource ('Create a Folder to group Threads') and states the grouping purpose, which immediately separates it from create_thread, move_thread, and the folder-management siblings. An agent can tell what it makes and why without opening the schema.

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

Usage Guidelines5/5

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

Explicitly sets a negative default ('Folders are optional: create one only when the person asks or their Folders clearly call for it') and then names the follow-up tools (move_thread, create_thread) that place Threads into the new Folder. Both the when and the when-not are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ThreadPage toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources