Skip to main content
Glama

mind_receipts

Read-onlyIdempotent

Retrieve verification receipts and their validity and verdicts to review proof from AI coding agent checks without rerunning them; use the results to plan further verification.

Instructions

Retrieve verification receipts and their validity and verdicts. Locally this reads the last verification receipt, if present; a configured hosted service supplies its own results. Validity does not rerun checks. Use proof to plan verification.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum receipts to return; local default is 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.63.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum receipts to return; local default is 20."
  2. Changed1 schema field changedv3.62.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only/idempotent annotations, the description discloses the local fallback ("reads the last verification receipt, if present") and a real behavioral caveat ("Validity does not rerun checks"), which prevents an agent from assuming fresh verification. It does not explain what happens when the hosted service is unreachable or how local and hosted results merge.

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?

Four short sentences, front-loaded with purpose and with no filler. The phrase "and their validity and verdicts" is slightly redundant, but overall it is dense and well ordered.

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 single-parameter, read-only tool with no output schema, the description covers source (local vs hosted), freshness semantics, and roughly what is returned (receipts with validity and verdicts). The structure of a receipt and any pagination behavior remain undefined, so the return shape is only partially characterized.

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?

With a single parameter at 100% schema description coverage, the schema already documents `limit` and its default. The description adds nothing about how `limit` interacts with the stated local behavior of reading "the last verification receipt" (singular), which is a mild inconsistency the schema alone doesn't resolve.

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?

Opens with a specific verb and resource ("Retrieve verification receipts") and scopes the content to validity and verdicts. It also implicitly separates itself from the sibling `proof` by assigning planning to that tool, though the boundary is stated as a bare instruction rather than an explicit contrast.

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?

The line "Use proof to plan verification" names an alternative and hints at the division of labor, and "Validity does not rerun checks" gives a meaningful constraint. However, no condition is given for when to reach for receipts versus proof, and no preconditions or exclusions are stated.

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