callimachus

Overview Schema Source Related Servers Discussions Admin

recurring_issues

Read-only

Identify recurring errors across sessions, with signatures, counts, affected sessions, and the commit, thread, or playbook that fixed them; check before retrying to avoid repeated failures.

Instructions

Errors the user keeps hitting across sessions: signature, counts, the sessions, and the fix (commit, thread, playbook) once a commit fixed one. Current repo by default; project="*" for all. Check before retrying.

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": "recurring_issues"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max error clusters (default 10, max 50).
`project`	No	Project path substring; omit for the current repo, "*" for all projects.
`since_days`	No	Look-back window in days (default 180).

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": {
+        "issues": {
+          "items": {
+            "properties": {
+              "count": {
+                "type": "integer"
+              },
+              "example": {
+                "type": "string"
+              },
+              "firstSeen": {
+                "type": "integer"
+              },
+              "fix": {
+                "properties": {
+                  "committedAt": {
+                    "type": "integer"
+                  },
+                  "sha": {
+                    "type": "string"
+                  },
+                  "shortSha": {
+                    "type": "string"
+                  },
+                  "subject": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "threadId": {
+                    "type": "integer"
+                  }
+                },
+                "required": [
+                  "sha",
+                  "shortSha",
+                  "subject",
+                  "committedAt",
+                  "threadId"
+                ],
+                "type": [
+                  "object",
+                  "null"
+                ]
+              },
+              "lastSeen": {
+                "type": "integer"
+              },
+              "playbook": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "threadIds": {
+                "items": {
+                  "type": "integer"
+                },
+                "type": "array"
+              },
+              "threads": {
+                "type": "integer"
+              }
+            },
+            "required": [
+              "example",
+              "count",
+              "threads",
+              "firstSeen",
+              "lastSeen",
+              "threadIds",
+              "fix",
+              "playbook"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "issues"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "notice": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "notice"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed5 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 error clusters to return (default 20)."New value: +"Max error clusters (default 10, max 50)."

changedInput schema / properties / project / description

Previous value: -"Path substring to scope to one repo. Omit to use the repo the server runs in; pass \"*\" for all projects."New value: +"Project path substring; omit for the current repo, \"*\" for all projects."

changedInput schema / properties / since_days / description

Previous value: -"How far back to scan, in days (default 180)."New value: +"Look-back window in days (default 180)."

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

Addedv0.8.2Jun 27, 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. The description adds that fixes are only attached once a commit resolved an issue and that scope defaults to the current repo, but the latter repeats the schema's project parameter text and nothing is said about cost or result size for a multi-session aggregation.

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 compact sentences, front-loaded with what the tool returns and followed by scope and the usage trigger. The telegraphic list style ("signature, counts, the sessions, and the fix") is efficient but slightly compressed at the cost of a little readability.

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, return values need not be spelled out, and all three optional parameters are documented in the schema. The description supplies the purpose and the pre-retry trigger, leaving only minor gaps such as how clusters are formed or how large the default result is.

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 description coverage is 100%, so limit, project, and since_days are already fully documented with defaults and bounds. The description only echoes the project="*" convention and adds no new meaning for limit or since_days; baseline 3 applies.

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?

The description names a specific resource (errors the user keeps hitting across sessions) and enumerates what each cluster carries: signature, counts, sessions, and the fix linkage (commit, thread, playbook). That is clearly more informative than a restated name. It doesn't explicitly contrast itself with a near sibling like recall_gotchas, so it falls short of a 5.

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?

"Check before retrying" gives a concrete trigger for calling the tool, and "Current repo by default; project="*" for all" clarifies scope selection. There is no explicit when-not guidance or named alternative tool, which keeps it below a 5.

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