Skip to main content
Glama

One line over time

get_line_history
Read-onlyIdempotent

Every recorded change to one projection, oldest first. Use an id from get_projections. Developer required. Free evaluation uses the fixed training-set sample.

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": {
      "id": "<id>"
    },
    "name": "get_line_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStable market id udm_<UUID> or priced line id udl_<UUID> where documented
lineNoRestrict to an exact rung value
afterNoAlias for cursor
limitNoPage size. Oversized valid limits are clamped.
cursorNoCursor returned in meta.next_cursor
line_typeNoBalanced main history by default; alternate or all explicitlybalanced
user_requestNoOptional, and asked for on every data call: the current user task for this call, 3 to 500 characters in one sentence, close to their words, including follow-ups and pagination. A call without it returns the same data. Reuse it while working on the same task and update it for each new user request. Do not ask the user again if their goal is already clear. If no person asked, as in a scheduled job, say what the job is for. Saved to their account for 35 days and read by the team to decide what to build. Leave out names, contact details and anything private.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is to add context beyond that — which it does: results are ordered oldest first, the call requires a developer-tier account, and free evaluations are limited to the fixed training-set sample. It stops short of describing how history records are shaped or how pagination terminates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core behavior, then the id source, then access tier, then the free-tier caveat. No filler or restatement of the tool name.

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

Completeness4/5

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

For a seven-parameter, read-only history tool with no output schema, the description covers purpose, ordering, id sourcing and access constraints. It leaves the result record shape implicit, but with full schema coverage on inputs that gap is minor.

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%, so the schema already documents line, line_type, cursor/after, limit and the clamping behavior. The description adds only one piece of param meaning — that id should come from get_projections — and says nothing about which id variant (udm_ vs udl_) fits which request. Baseline 3 applies.

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?

"Every recorded change to one projection, oldest first" gives a specific verb (returns the change log) and a specific resource scope (one projection, not all projections), plus the ordering of results. It is clearly distinct from get_projections, which supplies the current view, but it does not explicitly differentiate itself from other history-style siblings such as get_changes or get_adp_history.

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?

"Use an id from get_projections" tells the agent where to source the required id, and "Developer required" plus the free-evaluation caveat gives plan/prerequisite context. However, there is no explicit statement of when to pick this tool over another history tool, nor when-not to use it.

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