ThreadPage

Create a thread

create_thread

Idempotent

Start a Thread for a new subject. For progress on an existing subject, find its Thread (search, list_threads) and add a Note with create_note instead. destination_id: a Folder's id from list_folders, or null for the top level (needs whole-workspace access). Needs Can add notes or Can edit and organize. Answers a receipt with the new Thread's id (entity_id), revision and url; the same operation_id answers it again instead of creating a second Thread. Tell the person which Thread you created.

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

Input Schema

Name	Required	Description
`title`	Yes	1–200 characters.
`operation_id`	Yes	A new UUID for each write. After a lost answer, send the identical call with the same one, or check get_operation before writing again.
`destination_id`	No	A Folder's id, or null for the top level.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (idempotentHint, destructiveHint=false), the description explains the idempotency mechanism (the same operation_id answers again instead of creating a second Thread) and the shape of the response receipt (entity_id, revision, url). It also adds a post-call obligation to tell the person which Thread was created, which the annotations cannot convey.

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 sibling alternative, and every sentence carries information. The remaining text is a dense single block mixing permissions, return shape, and idempotency, which would read faster if segmented.

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?

For a write tool with no output schema, the description covers purpose, permissions, cross-tool routing, idempotent retry behavior, and the return receipt. Nothing an agent needs in order to call it correctly and report back is missing.

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

Parameters4/5

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

Schema coverage is 100%, so 3 is the baseline, but the description adds real meaning: destination_id is tied to a Folder id obtained from list_folders, with null meaning top level and requiring whole-workspace access. The operation_id explanation reinforces the retry-after-lost-answer semantics beyond the schema's wording.

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?

States a specific verb and resource ("Start a Thread for a new subject") and immediately contrasts it with the sibling create_note for existing subjects. An agent can tell it apart from create_note without opening either 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 names the alternative path: for progress on an existing subject, use search/list_threads to find the Thread then create_note. It also states the prerequisite access levels ("Can add notes or Can edit and organize") and the whole-workspace access needed when destination_id is null.

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

All ThreadPage tools Inspect

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.