Pidgeon

Hand a conversation to a person

update_thread

Idempotent

Who owns a conversation and where it has got to. status: "resolved" is Done in the inbox and "open" takes it out of Done; "human_review" puts it in Needs you. owner_type: "human" with status: "human_review" hands it to a person: the people who can answer as the address are notified, or only assignee_id when you name one. Say why in reason — it is in their notification. "agent" claims a conversation nobody has stepped into. A person replying from the inbox or a mail client takes it over themselves, and thread.updated tells you. While a person has it, you cannot send in it or take it back (403 taken_over); they hand it back.

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": {
      "id": "<id>"
    },
    "name": "update_thread"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`reason`	No
`status`	No
`owner_type`	No
`assignee_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedOct 20, 2026
- addedInput schema / properties / reason
```
Added value: +{
+  "maxLength": 500,
+  "type": "string"
+}
```
First observedOct 19, 2026

TDQS

A5/5.0

Behavior5/5

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

The description discloses crucial behavioral traits not covered by annotations, specifically notification logic and locking behavior. It informs the agent that the 'reason' is used for notifications and that the tool is transactional (preventing further edits while owned).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Despite its density, the description is highly concise and structured around workflow logic. Every sentence provides specific functional context—state, notification, or locking—with no wasted language.

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?

Given the complexity of state management and ownership, the description is extremely complete. It provides all necessary context for the AI agent to accurately map a complex conversational requirement onto the correct tool parameters and workflow.

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?

Since schema description coverage is 0%, the description must carry the burden. It fully compensates by detailing the meaning of the enum values (status/owner_type) and defining the functional use of fields like `reason` and `assignee_id` within the workflow.

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?

The tool purpose is extremely clear, defining the action as handing a conversation to a person. It distinguishes itself by detailing specific state transitions and ownership changes, which is crucial given the numerous similar 'update' and 'get' sibling tools.

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?

The description provides excellent usage guidelines by defining critical constraints. It explains when a conversation is locked ('403 taken_over') and how the status changes affect visibility (e.g., 'resolved' vs 'open'), guiding the agent on when this tool is applicable.

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

All Pidgeon 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.