Retrieve past messages from a Virtual Agent session using its conversation or session ID. Use it to review interaction logs and troubleshoot user issues.
Get conversation history for a Virtual Agent session
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max messages (default 50) | |
| conversation_id | Yes | Conversation sys_id or session ID |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds that it returns 'conversation history', which is slightly more specific than the name, but does not disclose pagination, return format, or other behavioral traits beyond what annotations provide.
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 a single, front-loaded sentence that is concise and free of unnecessary detail. It earns its place by clearly stating the tool's purpose without redundancy.
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?
Given the tool's simplicity, 2 parameters, and full schema coverage, the description is mostly complete. It could benefit from mentioning that it returns a chronological list of messages, but the name and 'history' make this highly inferable. The presence of sibling list_va_conversations also helps context.
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 coverage is 100%, with both parameters (conversation_id and limit) fully described. The description does not add parameter-specific meaning beyond the schema, so the baseline of 3 applies.
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 the tool retrieves conversation history for a Virtual Agent session, with a specific verb ('Get') and resource ('conversation history'). It distinguishes itself from the sibling 'list_va_conversations' by focusing on a single session's history rather than listing conversations.
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?
There is no explicit guidance on when to use this tool versus alternatives like list_va_conversations. The description implies usage by mentioning 'for a Virtual Agent session' but does not provide conditions, exclusions, or references to sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.