Skip to main content
Glama

Aidoptio: AI adoption catalog, estimates and advisor tools

Verify an Aidoptio evaluation report

verify_report
Read-onlyIdempotent

For a client, an auditor or a later buyer who holds an Aidoptio evaluation report. Give the report number and the method hash printed in it; the tool reads the public, append-only method log, verifies the whole hash chain and answers: match, match_superseded (a logged deviation replaced the hash), hash_mismatch or unknown_report, with the freeze date, whether the first vendor run came after the freeze, the deviations and the disclosure logged with the report. Read-only; nothing is stored.

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": {
      "report_id": "<report_id>",
      "method_hash": "<method_hash>"
    },
    "name": "verify_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYesReport number, e.g. AID-2027-001.
method_hashYesSHA-256 method hash from the report: 64 lowercase hexadecimal characters.

Output Schema

NameRequiredDescriptionDefault
rulesNo
statusYes
deviationsNo
disclosureNo
log_integrityYes
method_log_urlNo
policy_versionYes
disclosures_urlYes
preregistered_atNo
report_issued_atNo
first_vendor_run_after_freezeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description is not needed for safety profiling. It still adds real substance beyond them: it explains that the public append-only log is read and the whole hash chain checked, that match_superseded means a logged deviation replaced the hash, and that the freeze date, first-vendor-run timing, deviations and disclosure are returned. The final 'Read-only; nothing is stored' largely restates annotations.

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?

Two sentences, front-loaded with audience and precondition before the outcome list. The long comma-delimited outcome enumeration is dense but each item is informative; no filler beyond the redundant 'Read-only; nothing is stored'.

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?

An output schema exists, so return values need not be spelled out, and both required parameters are fully constrained in the schema. The description covers audience, prerequisites, mechanism and the possible verdicts — everything an agent needs to invoke and interpret the call.

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?

Schema description coverage is 100% — both report_id (with the AID-YYYY-NNN pattern and example) and method_hash (64 lowercase hex characters) are documented with format constraints. The description adds only the framing that the hash comes 'printed in it' and that a logged deviation may supersede it, which is useful context but marginal over the schema; baseline 3 applies.

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?

States a specific verb (verifies) and a specific resource (an Aidoptio evaluation report's method hash against the public append-only method log), and enumerates the four possible answers (match, match_superseded, hash_mismatch, unknown_report). This is clearly distinct from siblings such as verify_ai_text, which verifies text rather than a report hash.

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?

Names the intended callers and precondition explicitly: 'For a client, an auditor or a later buyer who holds an Aidoptio evaluation report. Give the report number and the method hash printed in it.' That tells an agent when the tool applies, but it does not say when not to use it or point to any alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources