Skip to main content
Glama

Claim history

facts.recall.history
Read-onlyIdempotent

Return a claim's raw events in order to audit every assert and retract, proving its log was not rewritten.

Instructions

Return the raw events of one claim, in order, exactly as they sit in the log. This is the auditable proof that nothing was rewritten: an assert, then a retract if there was one.

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": {
      "project": "<project>",
      "claim_id": "<claim_id>"
    },
    "name": "facts.recall.history"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject whose registry to read.
claim_idYesThe claim whose events to return.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the observation could be taken. NOT a judgement about what was observed: a cleanly received HTTP 500 is ok:true.
dataYesThe raw observation, or null when error is set.
toolYesFull tool name.
errorYesWhat prevented observing, if anything.
targetYesEffective arguments, redacted.
projectYesThe normalized project.
warningsYesNon-fatal notices.
age_basisYesWhich clock the age came from.
request_idYesThe request that produced it.
age_secondsYesSeconds since observed_at.
duration_msYesHow long the observation took.
observed_atYesISO 8601 with offset.
observation_idYesCitable id of this observation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, openWorldHint=false), so the bar is lower. The description still adds real behavioral context beyond them: the events are returned raw, ordered, unrewritten, and shaped as 'an assert, then a retract if there was one.' That is genuinely useful for interpreting the log.

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?

Two tight sentences, front-loaded with the core action and scope. Every clause earns its place and none of it repeats structured fields.

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?

With an output schema present, return values need not be described, and annotations carry the safety profile. The description adds the audit framing and event shape, leaving only the relationship to sibling recall tools unspecified — a minor gap for a simple two-parameter read.

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 100%, so the schema already documents both parameters ('project whose registry to read', 'claim whose events to return'). The description adds no further syntax or semantics beyond what the schema provides, which is the correct baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('Return the raw events of one claim, in order') with the scoping qualifier 'exactly as they sit in the log.' This implicitly separates it from facts.recall.query (current state) and facts.recall.assert/retract (mutations), but it never names a sibling, so the differentiation is inferential rather than explicit.

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 only implied via the audit framing ('auditable proof that nothing was rewritten'), which suggests a forensic/verification context. It never states when to prefer this over facts.recall.query or when it is unnecessary, so the agent must infer the boundary itself.

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