Skip to main content
Glama

get_item_history

Read-onlyIdempotent

Change events for an item: who changed what, when and why. Example: item_id, limit=10.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_id": "<item_id>"
    },
    "name": "get_item_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax events, default 20
item_idYesItem ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / item_id / description
      Previous value: -"The item ID"New value: +"Item ID"
    • changedInput schema / properties / limit / description
      Previous value: -"Max events to return (default: 20)"New value: +"Max events, default 20"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered without the description. The description's contribution is the return content shape ('who changed what, when and why'), which matters because no output schema exists, but it says nothing about ordering, pagination behavior, or whether the log is complete or truncated.

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?

Two short sentences, front-loaded with the return content, with no filler. The trailing 'Example: item_id, limit=10' is a fragment rather than a real example call and earns its place only marginally.

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

Completeness3/5

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

For a two-parameter read tool with annotations and full schema coverage, the description is close to sufficient: it tells the agent what comes back and shows the parameters. It leaves open ordering and truncation behavior, which an agent would want in order to interpret a truncated history as complete or partial.

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

Parameters3/5

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

Schema coverage is 100%, with 'limit' documented as max events defaulting to 20, so the schema does the heavy lifting. The description's 'limit=10' snippet illustrates invocation but adds no meaning about semantics or defaults beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and payload: change events for a given item, framed as 'who changed what, when and why'. That distinguishes it from siblings like get_item (current state) or get_collection_activity (collection scope), though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the audit framing ('who changed what, when and why'), which signals a history/change-log lookup rather than a current-state read. However, there is no explicit when-to-use, when-not-to-use, or named alternative such as get_item, so the agent must infer the routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources