Metis

Official

by BrightbeamAI

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Verify the evidence chain

audit_verify

Read-onlyIdempotent

Verify a workspace's hash-linked evidence chain and confirm any append-only ledger matches entry for entry before trusting the record or after an incident.

Instructions

Verify the workspace's whole hash-linked evidence chain and, when the workspace keeps an append-only ledger, check that the ledger agrees entry for entry. Use it before relying on the record, or after an incident. For the verified flag alone, use describe_workspace; to list recent entries, use audit_tail. A failed check is a normal result, verified false with the errors found, and the check reads every entry, so it takes longer as the chain grows.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`errors`	Yes	Each problem found. Empty when verified.
`entries`	Yes	Entries checked on the chain.
`verified`	Yes	True when every hash link verifies.
`ledger_agrees`	Yes	True when the ledger matches the chain entry for entry.
`ledger_entries`	Yes	Entries in the append-only ledger, when the workspace keeps one.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Oct 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), but the description adds genuinely useful behavior: a failed check is a normal result returned as verified=false with errors, and the check reads every entry so cost grows with chain length. Auth/permission requirements are not mentioned, but for a read-only verifier that is a minor gap.

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?

Three sentences, front-loaded with what it does, then routing, then failure semantics and cost. Every sentence carries distinct information with no padding.

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?

With an output schema present, return values need not be explained, yet the description still supplies the key interpretive fact that verified=false is a normal outcome. Alternatives and performance characteristics are covered, so an agent has everything needed to call and interpret it.

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?

The tool takes zero parameters, so the schema is trivially complete and the baseline is 4. The description correctly implies a whole-workspace, parameterless scan rather than a scoped one.

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?

Specific verb (verify) plus resource (the workspace's whole hash-linked evidence chain), and it even names the sub-case of ledger agreement. An agent can distinguish it from describe_workspace and audit_tail from the description alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States positive triggers ('before relying on the record, or after an incident') and explicitly routes to alternatives with their selecting conditions: describe_workspace for the verified flag alone, audit_tail for listing recent entries. Nothing is left to inference.

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

Deploy Server