USERDATA

history

Retrieve a newest-first record of actions performed within a session or project, enabling review of prior research steps and decisions.

Instructions

Returns what was done, newest first, for a session or project.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`project_id`	No
`session_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the sort order ('newest first'), which is genuinely useful, but it omits whether the operation is read-only, how the default limit of 100 behaves, what happens when both or neither of session_id/project_id is set, and anything about output volume or pagination.

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?

The description is a single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the under-specification noted in other dimensions rather than reflecting thoroughness.

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

Completeness2/5

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

The presence of an output schema means return contents need not be explained, which lowers the bar. Even so, for a 3-parameter tool with zero schema coverage and no annotations, the description leaves too much undefined: the meaning of limit, the session/project selector behavior, and any read-safety context are all missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for all three parameters and does not. It implies session_id and project_id exist via 'for a session or project' but says nothing about their interaction or mutual exclusivity, and it never mentions 'limit' or its default of 100. An agent must open the schema and still guess at parameter behavior.

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 says it 'Returns what was done' with a stated ordering ('newest first') and scope ('for a session or project'), so the general idea—an activity history read—comes through. However, 'what was done' is vague about what a record actually is (log entries? events? run results?), especially with siblings like 'log' and 'add_note' in the same namespace. It does not distinguish this tool from those siblings.

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?

There is no explicit statement of when to use this tool versus alternatives, and no prerequisites. The only implicit guidance is the mention of 'session or project', which hints at the two filtering modes but never says which to choose or what happens if neither is supplied. No exclusions or recommendations are given.

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