Skip to main content
Glama

Explain Claim

proofspec_explain

Evaluates a claim against its evidence specification, returning the policy, dependencies, limitations, evidence, and receipts needed to verify it.

Instructions

Evaluate the specification and return one claim with its policy, dependencies, limitations, evidence, and receipts.

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": {
      "claim": "<claim>"
    },
    "name": "proofspec_explain"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYes
configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully lists what the claim result includes, such as policy, dependencies, limitations, evidence, and receipts, but it does not disclose whether the operation is read-only, what permissions it requires, or how errors 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?

The definition is a single front-loaded sentence with no filler, and the list of return components is relevant. Its main issue is under-specification, not unnecessary wording.

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?

For a tool with two parameters, no annotations, and no output schema, the description omits parameter meaning, usage context, and operational safety. It gives some useful return-content detail but is not complete enough for reliable invocation.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description never explains the required 'claim' parameter or the optional 'config' parameter. Saying it will 'return one claim' may even be misread as describing output rather than input, so the description does not compensate for the schema gap.

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 states a verb, 'evaluate,' and a resource, 'specification,' and lists the result components. However, 'claim' and 'specification' are not defined, and it does not distinguish this tool from siblings such as proofspec_check or proofspec_validate.

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 guidance, no prerequisites, and no comparison to the sibling checking, rendering, or validation tools. The agent must infer the appropriate context from the name alone.

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