Skip to main content
Glama

LiquiLens Failure Radar

Verify the published record

verify_published_record
Read-onlyIdempotent

Check ledger hash chains, enabled signatures and anchors; retain failures. Record integrity, not economic accuracy.

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": "verify_published_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
streamNoledger stream name to verifymfi_watchlist

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / stream / description
      Previous value: -"ledger stream name to verify (default 'mfi_watchlist')"New value: +"ledger stream name to verify"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuine behavioral detail beyond that — failures are retained rather than silently dropped — plus what checks are performed. It says nothing about how results are surfaced, cost, or what a partial chain failure implies.

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 compact sentences, front-loaded with the checks performed and followed by the scope limit; no filler or repetition. Slightly telegraphic fragments ('retain failures') cost a word of clarity but nothing is wasted.

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

Completeness4/5

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

For a single-parameter, annotation-rich, non-destructive verification tool with no output schema, the description covers what is checked, what is kept, and what is out of scope. The remaining gap is the shape of the verification outcome (pass/fail per check? aggregate?), which an agent would have to discover by calling it.

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% and the single parameter 'stream' carries its own description and default, so the schema does the heavy lifting. The description never mentions the stream argument, what happens when it is omitted, or whether other streams exist. Baseline 3 is appropriate.

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?

States a concrete verb ('Check') with enumerated resources — ledger hash chains, enabled signatures, anchors — so an agent knows exactly what is being validated. The second sentence bounds the scope to record integrity rather than economic accuracy, which further sharpens purpose. It does not name or contrast any sibling, keeping it just short of a 5.

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?

'Record integrity, not economic accuracy' is the only routing signal: it tells the agent this is a structural/ledger check rather than a substantive review, implicitly distinguishing it from the many board/evidence siblings. There is no explicit when-to-use or when-not-to-use statement, and no alternative is named, so guidance remains implied rather than stated.

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.