Retrieves the harvest and change history for an order.
[DEPRECATED] Get an Order's harvest and change history
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": "GetOrderHistory"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for behavioral transparency. The description states it 'Get's' history, implying a read operation, but does not confirm read-only behavior, potential side effects, authorization requirements, or any other behavioral details. 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 a single sentence with the deprecation warning front-loaded. Every word earns its place—there is no fluff or redundancy. It is as concise as possible.
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 is deprecated and has no output schema, the description should provide more context: why it's deprecated, what the alternative is, and what 'harvest and change history' means. It fails to guide the agent effectively, especially with many sibling tools that may confuse.
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?
The tool has zero parameters, and the schema coverage is 100% (vacuously). The description does not need to add parameter meaning. However, it could clarify how the order is identified (e.g., implicitly via context), but it doesn't. Still, the baseline for zero parameters is 4, and no confusion is introduced.
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 verb and resource: 'Get an Order's harvest and change history'. However, it does not differentiate from the sibling tool GetOrderHistoryV3, which serves the same purpose but is not deprecated. The purpose is clear but lacks sibling 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?
No usage guidelines are provided. The description does not mention when to use this tool versus alternatives, nor does it indicate that this tool is deprecated and that GetOrderHistoryV3 should be used instead. The agent receives no guidance on appropriate usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.