Skip to main content
Glama

Check Proofspec

proofspec_check

Evaluates claims and appends independently labelled evidence receipts, then verifies the hash-chained ledger and returns a complete report for auditing README, release, or product-page assertions.

Instructions

Evaluate every claim, append independently labelled evidence receipts, verify the ledger, and return the complete report.

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

Input Schema

NameRequiredDescriptionDefault
configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose a meaningful trait beyond the name: the tool appends 'independently labelled evidence receipts', which signals a persistent write/side effect, and it returns a full report. It stops short of stating whether the append is idempotent, requires write authorization, mutates shared state, or how failures mid-ledger are handled.

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?

A single sentence with no filler, and the action sequence is front-loaded in execution order. It is a four-clause run-on rather than a structured list, but nothing is wasted.

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 tool with no annotations, no output schema, and one undocumented parameter, the definition is incomplete: it omits what 'config' should contain, what a ledger or evidence receipt actually is, and what the returned report looks like. The sentence is accurate but insufficient for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% for the single 'config' parameter, and the description never mentions it, so the agent learns nothing about its format, whether it is required, or what it configures. The burden falls entirely on an unlabeled string field, which is a clear gap at this coverage level.

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 lists concrete actions (evaluate claims, append evidence receipts, verify a ledger, return a report), so it is more than a restatement of the name. However, the core nouns ('claims', 'ledger', 'evidence receipts') are undefined jargon, and the relationship to siblings is unaddressed: 'verify the ledger' plausibly overlaps with proofspec_validate and 'report' overlaps with proofspec_render, leaving the agent unable to tell which tool to pick.

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 when-to-use context, no stated preconditions, and no reference to any of the three sibling tools. The agent must infer from the name alone whether this is the primary entry point in the proofspec workflow or a downstream verification step.

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