Skip to main content
Glama

job_history

Read-only

Lists receipts for recent deterministic local jobs, so you can review outcomes and verify what executed in approved workspaces.

Instructions

List receipts for recent local deterministic jobs

Tool call template

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": "job_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds that results are scoped to local, deterministic, recent jobs, which is meaningful context beyond the annotations. It omits retention window, ordering, truncation behavior at the limit ceiling, and what a receipt contains.

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?

One short sentence, front-loaded with the verb and resource, with no filler or repetition. It is efficient, though the terseness comes at the cost of the missing detail noted elsewhere.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of explaining what a receipt looks like and in what order results arrive; it says none of that. It also leaves the limit default and truncation semantics unstated, which is a real gap for the only parameter.

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 description coverage is 0%, so the single `limit` parameter is documented only by its type and 1-100 bounds. The description never mentions pagination, default value, or that results are capped, leaving the agent to infer that limit controls how many receipts come back. Baseline 3 for a one-parameter tool with a partially self-explanatory schema.

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

Purpose3/5

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

The description gives a verb ("List") and a resource ("receipts for recent local deterministic jobs"), which is better than a tautology. However, "receipts" and "deterministic jobs" are undefined jargon, and nothing distinguishes this from siblings like list_job_recipes or run_job. An agent can guess it is a history/listing tool but cannot confidently predict its contents.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no precondition or exclusion, and no named alternative. The word "recent" hints at a time scope but gives no threshold. The agent must infer usage purely from the title-adjacent phrasing.

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