Skip to main content
Glama

Nalvorn Checks

verify_manifest

Read-only

Compare a list of files with a sha256 manifest and report every mismatch Free of charge.

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": {
      "manifest": "<manifest>",
      "files": "<files>"
    },
    "name": "verify_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesObject mapping file paths to actual sha256 digests
manifestYesObject mapping file paths to expected sha256 digests

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description is consistent with a read-only comparison that reports mismatches. It adds a little beyond the annotations by indicating that all mismatches are reported (not just the first), but it never explains the shape of that report, and the pricing phrase is noise rather than behavioral context.

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?

The core sentence is front-loaded and efficient, but "Free of charge" is marketing filler that occupies space without informing invocation. The mixed capitalization mid-sentence also reads as an artifact rather than deliberate structure.

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 two-parameter, fully documented, read-only comparison tool with no output schema, the description covers the essential contract. The only real gap is that an agent cannot anticipate the format of the mismatch report, which matters slightly more here because no output schema exists.

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%, so both parameters are already documented, and the description adds nothing about digest format, whether paths are absolute or relative, or how the files object keys must align with manifest keys. Baseline 3 applies when the schema carries the semantic load; here it does so completely.

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?

"Compare a list of files with a sha256 manifest and report every mismatch" gives a concrete verb (compare), two named resources (files, sha256 manifest), and the outcome (mismatch report). It is clear what the tool does, but it does not distinguish itself from sibling verification tools such as receipt_verify or package_check, so it falls 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 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 prerequisites, and no mention of any alternative tool. An agent must infer from the name alone that this is the right choice for hash-manifest verification, and the trailing "Free of charge" does not help routing decisions.

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