callimachus

Overview Schema Source Related Servers Discussions Admin

recent_threads

Read-only

Retrieve recently updated conversation threads, newest first, and filter them by source, project path, starred status, or tags to review recent work.

Instructions

The user's most recently updated threads, newest first, filterable by source, project path, starred or tags. Use to see what they worked on lately.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_threads"
  }
}

Input Schema

Name	Required	Description
`tags`	No	Only threads with ANY of these tags (see list_tags).
`limit`	No	Max threads (default 10, max 50).
`project`	No	Project path substring.
`sources`	No	Source filter (see search_threads). Empty = all.
`starred`	No	Only starred threads.

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": {
+        "threads": {
+          "items": {
+            "properties": {
+              "id": {
+                "type": "integer"
+              },
+              "messageCount": {
+                "type": "integer"
+              },
+              "projectPath": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "source": {
+                "type": "string"
+              },
+              "starred": {
+                "type": "boolean"
+              },
+              "title": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "updatedAt": {
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "id",
+              "source",
+              "title",
+              "projectPath",
+              "messageCount",
+              "updatedAt",
+              "starred"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "threads"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "notice": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "notice"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed7 schema fields changedv0.11.3Nov 6, 2026

removedInput schema / $schema

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

changedInput schema / properties / limit / description

Previous value: -"Max threads to return (default 20)."New value: +"Max threads (default 10, max 50)."

changedInput schema / properties / project / description

Previous value: -"Substring-match the project path (e.g. a repo path) to scope results."New value: +"Project path substring."

changedInput schema / properties / sources / description

Previous value: -"Optional source filter (see search_threads). Empty = all sources."New value: +"Source filter (see search_threads). Empty = all."

changedInput schema / properties / starred / description

Previous value: -"If true, return only threads the user has starred."New value: +"Only starred threads."

changedInput schema / properties / tags / description

Previous value: -"Only threads tagged with ANY of these tags (see list_tags). Empty = all."New value: +"Only threads with ANY of these tags (see list_tags)."

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

First observedv0.5.0Jun 19, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds ordering (newest first) but nothing about return shape, pagination, or what an empty result means; with no output schema reference needed, this is adequate but thin.

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?

Two short sentences, front-loaded with what the tool returns and then why to call it. Nothing is wasted, though the filter list slightly duplicates the schema.

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, full parameter coverage, and read-only annotations, an agent has everything needed to invoke this correctly. The only missing element is sibling routing guidance.

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%, so every parameter is already documented in the schema, including limits and defaults. The description only restates the filter names (source, project path, starred, tags), adding no syntax or interaction detail beyond the schema baseline.

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?

States a specific resource (the user's threads) plus scope (most recently updated, newest first) and enumerates the filter dimensions. Recency ordering implicitly separates it from search_threads, though no sibling is named explicitly.

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?

'Use to see what they worked on lately' gives a clear situational use. It stops short of naming alternatives (e.g., search_threads when the user knows what they're looking for) or saying when not to use this tool.

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