Skip to main content
Glama

verify_bundle

Verifies one Canari bundle offline with DSSE/Ed25519 signature and schema checks, returning a per-check breakdown.

Instructions

Offline verification of one canari bundle: DSSE/Ed25519 signature + schema + per-check breakdown.

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": {
      "bundle_path": "<bundle_path>",
      "key_path": "<key_path>"
    },
    "name": "verify_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_pathYes
bundle_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation is offline and lists the verification components, which is useful, but omits whether the tool is read-only, what happens on failure, and full return semantics (though 'per-check breakdown' hints at output).

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?

A single well-structured sentence that front-loads the core purpose and lists verification checks without filler.

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

Completeness3/5

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

For a two-parameter verification tool with no annotations or output schema, the description gives adequate purpose and hints at return values (per-check breakdown). However, it lacks parameter semantics and behavioral details needed for confident invocation.

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 0%, and the description never mentions bundle_path or key_path, leaving both required parameters completely unexplained beyond their names. It does not compensate for the schema gap.

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 specific verb (verification) and resource (one canari bundle), and enumerates the checks performed (DSSE/Ed25519 signature, schema, per-check breakdown). The scope is clear, but it does not explicitly differentiate from siblings like gate_check or store_summary.

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?

Provides no guidance on when to use this tool versus alternatives, and no prerequisites or when-not conditions. Only an implied use case can be inferred from the purpose statement.

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

Deploy Server

Other Tools