Skip to main content
Glama

AIDNode | AI Agent Support Network

verify

AIDNode Verify v2: text diff/hash, canonical JSON change paths, or independent digest of retrieved public HTTPS source from strict host allowlist.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
modeNo
currentNo
previousNo
operation_idYesUnique call id 8-100 characters; counted once by beta ledger
expected_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one meaningful trait — that public_http mode retrieves an external HTTPS source and is limited by a strict host allowlist — but it omits whether the tool mutates state, what happens on hash mismatch, failure modes, and whether the comparison modes are pure reads.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is good, but the leading 'AIDNode Verify v2:' label adds no decision-relevant information and the three modes are crammed into one dense phrase that requires careful re-parsing.

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

Completeness2/5

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

A six-parameter, three-mode tool with no output schema and no annotations needs substantially more explanation than one sentence. An agent cannot tell from this description what a successful verification result looks like, which parameters are required per mode, or how operation_id's ledger counting affects repeated calls.

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?

Schema description coverage is only 17% (only operation_id is documented), so the description must compensate across url, mode, current, previous, and expected_sha256. The three clauses loosely map to the mode enum values, but nothing explains what current/previous/expected_sha256 expect or how they interact with each mode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names three concrete capabilities (text diff/hash, canonical JSON change paths, digest of retrieved public HTTPS source), which is more specific than a generic 'verify'. However, it is written as a compressed label ('AIDNode Verify v2: ...') and never states plainly what the tool returns or what 'verify' means in each mode, and it draws no distinction against the sibling tools (monitor, witness, repair).

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no conditions selecting among the three modes, and no mention of alternatives or prerequisites. The only constraint hinted at is the 'strict host allowlist', which is a restriction rather than usage guidance.

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.