zetesis

verify_attestation

Read-only

Confirm that an evaluation's claim, evidence, and conclusion remain unchanged since signing. Independently verify any attestation without an account.

Instructions

Verify a Zetesis attestation, confirming an evaluation's claim, evidence, and conclusion have not been altered since it was signed. Use when someone has a Zetesis dossier or attestation and wants to independently re-check it. No account needed.

Args: attestation_json: the full attestation object as JSON text.

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": {
      "attestation_json": "<attestation_json>"
    },
    "name": "verify_attestation"
  }
}

Input Schema

Name	Required	Description	Default
`attestation_json`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 28, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds context about what is verified (claim, evidence, conclusion) and that no account is needed. No contradictions but does not disclose additional behaviors beyond annotations.

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?

Two sentences plus an Args line. All front-loaded: purpose first, then usage, then parameter. Every sentence adds value. No redundancy.

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?

Tool has 1 simple parameter, annotations provide safety profile, and description covers purpose, usage, and parameter. Output schema exists (not shown). No gaps for the given complexity.

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

Parameters4/5

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

Schema coverage is 0%, so description carries full burden. Description explains 'attestation_json' as 'the full attestation object as JSON text,' adding meaning beyond the schema's type and title. Single parameter well-documented.

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 clearly states the verb 'verify' and the resource 'attestation', with specific details about confirming integrity of claim, evidence, and conclusion. It distinguishes from siblings like evaluate_claim and check_evaluation.

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?

Explicitly states when to use: someone has a Zetesis dossier or attestation and wants independent re-check. Also notes 'No account needed,' implying no authentication required. Could be improved with explicit alternatives or when-not-to-use.

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

Deploy Server