Skip to main content
Glama

Validate Proofspec

proofspec_validate

Validates a configuration by checking unique IDs and an acyclic claim graph without verifying evidence, so you can catch structural errors before evidence checks.

Instructions

Validate a Proofspec configuration, including unique IDs and an acyclic claim graph, without checking evidence.

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_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose an important boundary: evidence is not verified, only structure. It does not state whether the call is read-only, what happens when validation fails (returned errors vs. thrown exception), or what the result contains, leaving meaningful behavioral gaps for a mutation-free but side-effect-ambiguous tool.

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?

A single sentence that front-loads the verb and resource, then layers the check scope and the explicit exclusion. Nothing is redundant or padded.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and an undocumented parameter, the description should do more: it explains validation scope well but omits the input format and the shape of the result. Adequate for understanding intent, insufficient for calling the tool correctly on the first attempt.

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?

The single parameter 'config' has 0% schema description coverage, and the description only repeats the word 'configuration' without clarifying whether it is raw JSON/YAML text, a file path, or an identifier — a critical distinction given the parameter is typed as a string with minLength 1. It also leaves the empty required list unexplained (required: 0 despite one meaningful parameter).

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?

The description gives a specific verb ('Validate') and resource ('Proofspec configuration') and even enumerates the checks performed ('unique IDs and an acyclic claim graph'), which is more than the title restates. It does not, however, distinguish itself from the similarly named sibling proofspec_check, so an agent cannot tell the two apart from this text alone.

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 clause 'without checking evidence' is a useful negative scope marker implying this tool is for structural validation rather than evidence verification. There is no explicit when-to-use guidance, no statement of prerequisites, and no routing to a sibling such as proofspec_check or proofspec_explain.

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