Load the full message history for a local chat session by name and return a formatted transcript with timestamps and roles, or a not-found message.
Return the full message history for a local chat session.
Args:
session: Session name to load from `chats/{session}.json` (default `default`).
Returns:
Formatted transcript with timestamps and roles, or a not-found message.
| Name | Required | Description | Default |
|---|---|---|---|
| session | No | default |
Changes observed during successful MCP inspections.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses read-only nature (confirmed by annotations), format of return (timestamps and roles), and behavior on not-found. Adds detail beyond annotations.
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?
Extremely concise with clear sections for description, args, and returns. No unnecessary words.
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?
Adequate for a simple read-only tool with one parameter. Covers purpose, parameter, and return format. No output schema, so description handles it well.
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?
Explains the session parameter as a file path pattern, adding meaning beyond the schema alone. Schema coverage is 0%, so description provides essential semantics.
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?
Clearly states it returns full message history for a local chat session. Distinguishes from siblings like clear_chat_history and list_chat_sessions by specificity to a single session, but lacks explicit differentiation.
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?
Implies usage for retrieving history of a specific session, but no guidance on when to use versus alternatives like retrieve_stateful_response or list_chat_sessions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.