Retrieve tasks from M3 Memory with optional filters for state, owner, or parent, sorted by newest updates first.
List tasks with optional filters. Newest updated first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | No | ||
| timeout | No | ||
| database | No | ||
| as_records | No | ||
| owner_agent | No | ||
| parent_task_id | No |
Changes observed during successful MCP inspections.
v0.1.20Input schema / properties / as_recordsAdded value: +{
+ "default": false,
+ "title": "As Records",
+ "type": "boolean"
+}v0.1.9v0.1.7v0.1.2Input schema / properties / timeoutAdded value: +{
+ "default": 30,
+ "title": "Timeout",
+ "type": "number"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for disclosing behavior. It does state 'Newest updated first', which is a useful behavioral detail, but it omits critical aspects like whether the operation is read-only, any side effects, permission requirements, or what happens with filter combinations. For a list operation, the description gives minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very concise, consisting of a single sentence with no fluff. The primary verb and resource are front-loaded. However, the structure is minimal and does not provide any breakdown of filters or usage context, which is acceptable given its brevity but could be improved with a second sentence explaining the filter options.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 7 parameters, no output schema, and no annotations. The description is severely incomplete: it does not explain what the output looks like, how filters interact, what each parameter means, or when to use this tool over siblings. An agent would be left guessing about the semantics of the parameters and the expected result format, making the description insufficient for effective tool selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% – the schema provides no descriptions for the 7 parameters. The description only says 'optional filters' without explaining any of the parameters (limit, state, timeout, database, as_records, owner_agent, parent_task_id). This is a critical gap; the description must compensate but fails to provide any semantic meaning for the parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb and resource: 'List tasks' with optional filters. It is not a tautology and distinguishes itself from siblings like agent_list or memory_get by focusing on tasks. However, it does not explicitly differentiate itself from other list-type tools or clarify the scope of 'tasks', so it is slightly below a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions 'optional filters' but provides no guidance on when to use this tool versus alternatives such as agent_list or memory_get. There are no explicit exclusions or contextual cues. The only implied usage is that it is for tasks, but no reasoning or selection criteria are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.