Darwin

List act history

list_act_history

Read-onlyIdempotent

List private threads for the authorized Darwin account. This is the same bounded read as list_threads.

Input Schema

Name	Required	Description
`limit`	No	Maximum entries to return, from 1 to 100.
`cursor`	No	Opaque cursor from the previous page.
`archived`	No	Filter by archived state; omit to use the default history view.
`targetAgent`	No	Filter history to threads with this target agent identifier.
`needsAttention`	No	Filter by whether a thread needs attention from the caller.

Output Schema

Name	Required	Description	Default
`cursor`	Yes
`threads`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 27, 2026

addedInput schema / properties / archived / description

Added value: +"Filter by archived state; omit to use the default history view."

addedInput schema / properties / cursor / description

Added value: +"Opaque cursor from the previous page."

addedInput schema / properties / limit / description

Added value: +"Maximum entries to return, from 1 to 100."

addedInput schema / properties / needsAttention / description

Added value: +"Filter by whether a thread needs attention from the caller."

addedInput schema / properties / targetAgent / description

Added value: +"Filter history to threads with this target agent identifier."

Changed1 schema field changedOct 5, 2026

removedInput schema / properties / agent

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

Changed22 schema fields changedOct 1, 2026

removedInput schema / properties / actingAiId

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

addedInput schema / properties / agent

Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
+  "type": "string"
+}

removedInput schema / properties / attention

Removed value: -{
-  "type": "boolean"
-}

removedInput schema / properties / limit / default
```
Removed value: -50
```
addedInput schema / properties / needsAttention
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / targetAgent

Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
+  "type": "string"
+}

removedInput schema / properties / targetAiId

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

removedInput schema / required
```
Removed value: -[
-  "actingAiId"
-]
```

addedOutput schema / properties / cursor

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 1,
+      "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

removedOutput schema / properties / nextCursor

Removed value: -{
-  "anyOf": [
-    {
-      "maxLength": 200,
-      "minLength": 1,
-      "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / threads / items / properties / actingAiId

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

removedOutput schema / properties / threads / items / properties / attention
```
Removed value: -{
-  "type": "boolean"
-}
```

removedOutput schema / properties / threads / items / properties / cursor

Removed value: -{
-  "maxLength": 200,
-  "minLength": 3,
-  "pattern": "^.+:(0|[1-9][0-9]*)$",
-  "type": "string"
-}

removedOutput schema / properties / threads / items / properties / goalId

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

addedOutput schema / properties / threads / items / properties / needsAttention
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / threads / items / properties / revision

Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

addedOutput schema / properties / threads / items / properties / targetAgent

Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
+  "type": "string"
+}

removedOutput schema / properties / threads / items / properties / targetAiId

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

addedOutput schema / properties / threads / items / properties / thread

Added value: +{
+  "maxLength": 200,
+  "minLength": 1,
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
+  "type": "string"
+}

removedOutput schema / properties / threads / items / properties / threadId

Removed value: -{
-  "maxLength": 200,
-  "minLength": 1,
-  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
-  "type": "string"
-}

changedOutput schema / properties / threads / items / required

Previous value: -[
-  "threadId",
-  "goalId",
-  "actingAiId",
-  "targetAiId",
-  "revision",
-  "archived",
-  "attention",
-  "cursor",
-  "createdAt"
-]New value: +[
+  "thread",
+  "targetAgent",
+  "archived",
+  "needsAttention",
+  "createdAt"
+]

changedOutput schema / required

Previous value: -[
-  "threads",
-  "nextCursor"
-]New value: +[
+  "threads",
+  "cursor"
+]

AddedSep 29, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds the account scoping ('authorized Darwin account') and the 'bounded read' notion, but says nothing about pagination behavior or result shape beyond what the output schema covers.

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 the core action and scope, with no filler. Only mild waste in the comparison to a tool the agent cannot see.

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

Completeness3/5

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

Rich annotations and an output schema cover safety and returns, and all parameters are documented. What remains missing is a resolution of the 'act history' vs 'private threads' terminology and any explicit routing versus sibling list/get tools.

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% – limit, cursor, archived, targetAgent, and needsAttention are all documented in-schema. The description adds no additional meaning about filters or paging, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('List') and a resource, but the resource is described as 'private threads' while the tool name and title say 'act history' – the agent is left to reconcile that mismatch. It does not distinguish itself from siblings such as get_thread or list_search_history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

'This is the same bounded read as list_threads' gestures at usage, but list_threads is not among the available sibling tools, so the reference cannot be followed. No explicit when-to-use or when-not-to-use guidance against the tools the agent can actually see.

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

All Darwin tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?