callimachus

Overview Schema Source Related Servers Discussions Admin

get_thread

Read-only

Reads one past conversation thread as a packed markdown transcript, trimmed to a character budget, so agents can recall full context beyond a short recap.

Instructions

Read one thread as a packed markdown transcript, trimmed to budget chars (default 24000); the text and structured markdown both hold it. Try get_thread_knowledge first for a short recap.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "get_thread"
  }
}

Input Schema

Name	Required	Description	Default
`budget`	No	Max chars to return (default 24000, max 96000).
`thread_id`	Yes	Thread id from a search or recent result.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.4Nov 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "markdown": {
+          "type": "string"
+        },
+        "threadId": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "threadId",
+        "markdown"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "notice": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "notice"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed4 schema fields changedv0.11.3Nov 6, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

addedInput schema / properties / budget

Added value: +{
+  "description": "Max chars to return (default 24000, max 96000).",
+  "format": "uint32",
+  "minimum": 0,
+  "type": [
+    "integer",
+    "null"
+  ]
+}

changedInput schema / properties / thread_id / description

Previous value: -"The thread id from a search result."New value: +"Thread id from a search or recent result."

removedInput schema / title
```
Removed value: -"GetThreadArgs"
```

First observedv0.5.0Jun 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: output is truncated to `budget` chars (default 24000) and the content appears both as text and in a structured `markdown` field, which tells the agent how to consume the result. It omits error/not-found behavior for a mutation-free read, a minor gap.

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?

One front-loaded sentence capturing purpose, output format, and truncation, followed by a single routing clause. No wasted wording.

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

Completeness4/5

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

With an output schema present and 100% param coverage, the description only needs to convey behavior and routing, which it does. It explains truncation and the dual text/markdown encoding, though it says nothing about how truncation affects very large threads beyond the char cap.

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 coverage is 100% and the schema already documents `budget` (max chars, default 24000, max 96000) and `thread_id`. The description only reinforces that `budget` controls transcript trimming, which is marginal added meaning beyond the schema text.

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 (read one thread) plus the exact return shape (packed markdown transcript trimmed to budget chars), and names the sibling it is not (get_thread_knowledge). An agent can distinguish it from the recap tool 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 Guidelines4/5

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

Gives an explicit routing rule: try get_thread_knowledge first for a short recap, implying this tool is for full transcripts. No explicit when-not conditions or other alternatives, but the primary selection decision is covered.

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