Skip to main content
Glama

Why

why
Read-onlyIdempotent

Trace a claim's history: current status, predecessors it replaced with recorded reasons, and closing reason. Use before re-opening settled claims to avoid re-litigating closed questions.

Instructions

Explain a claim's history. Read-only; writes nothing. Returns the claim's current title and status, then one line per predecessor it replaced with the reason recorded at the time, then its closing reason if it has been resolved. A claim that replaced nothing says so explicitly ('supersedes nothing — original decision') rather than returning an empty result, so a blank answer always means the lookup failed, never that the history is empty. Accepts a claim id or a unique substring of its title; an ambiguous substring returns the candidate ids instead of guessing, and no match says so. Call it before re-opening anything that looks settled — the answer is often that it was already decided, reversed once, and why, which is the difference between a considered change and re-litigating a closed question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesClaim id (for example d4) or a unique substring of its title. Substrings are matched case-insensitively against both id and title, so a distinctive few words are usually enough.
projectNoNamed project in the central store. Omit inside a repo that has .continuity/, where state is found by walking up from the working directory.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / id / description
      Previous value: -"Claim id or a unique substring of its title."New value: +"Claim id (for example d4) or a unique substring of its title. Substrings are matched case-insensitively against both id and title, so a distinctive few words are usually enough."
  2. Changed2 schema fields changedv1.1.1
    • addedInput schema / properties / id / description
      Added value: +"Claim id or a unique substring of its title."
    • changedInput schema / properties / project / description
      Previous value: -"Named project (central store). Omit inside a Claude Code repo."New value: +"Named project in the central store. Omit inside a repo that has .continuity/, where state is found by walking up from the working directory."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description details the return sequence, the explicit 'supersedes nothing' behavior, the blank-result meaning, and the ambiguity/no-match handling. This is substantial behavioral disclosure that helps an agent interpret results correctly.

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?

The description is longer than minimal but every sentence adds value: purpose, return format, edge cases, input semantics, and usage context. It is front-loaded and well-organized, though a few clauses could be tightened without losing meaning.

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

Completeness5/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 correctly carries the burden of explaining return values and failure modes. It covers current title/status, predecessor lines, closing reasons, empty-history semantics, lookup failure, and ambiguity. For a read-only lookup tool, nothing essential is missing.

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

Parameters5/5

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

The input schema already documents both parameters fully (100% coverage), and the description adds meaningful semantics: substring matching is case-insensitive, ambiguous substrings return candidate ids, and no match is reported explicitly. This goes beyond the schema and prevents incorrect assumptions.

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

Purpose5/5

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

The description opens with 'Explain a claim's history,' a specific verb and resource, and clarifies it is read-only. It clearly separates this tool from the write-oriented siblings like record_decision, freeze_claim, and resolve_claim, and from list_projects.

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

Usage Guidelines4/5

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

The description gives explicit guidance: 'Call it before re-opening anything that looks settled' and explains why the history matters. It does not name alternatives or state when not to use it, but the context is clear enough for an agent to route correctly.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikcena01/ai-continuity-plugin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server