Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

batch_verify_manuals

Read-only

Verify buyer-facing manuals across up to 500 PDFs or 3MFs in one batch, checking release IDs, embedded metadata, or PDF hashes to confirm each file matches its intended release.

Instructions

Batch buyer-facing verification across many PDFs / 3MFs.

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": {
      "paths": "<paths>"
    },
    "name": "batch_verify_manuals"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesLocal paths to verify. Each path goes through the same resolution order as the single-file tool (release_id → 3MF embed → bare-PDF hash lookup). Capped at 500 entries; longer batches return INVALID_INPUT with the cap mentioned.
release_idNoOptional shared release identifier. When supplied, every path is verified against this release. When ``None``, each file uses the fall-through resolution independently — useful when a fulfillment run mixes versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so the safety profile is clear. The description adds batch scope and file types, but does not mention permissions, failure handling, or what 'buyer-facing verification' actually checks.

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?

It is a single front-loaded fragment with no wasted words. The brevity is efficient, though the sentence does not fully stand on its own as a complete usage statement.

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 relatively simple two-parameter batch tool, the schema and annotations carry most of the needed detail. The description still leaves 'buyer-facing verification' ambiguous and does not clarify how this relates to the single-file tool or verify_manual_authenticity.

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 the parameters are fully documented in the schema, including the 500-entry cap and shared release_id semantics. The description adds no parameter meaning beyond the schema, which is acceptable at the baseline when the schema does the heavy lifting.

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 scope ('many PDFs / 3MFs') with a clear batch qualifier. However, it does not distinguish this from sibling verification tools such as verify_manual_authenticity or the implied single-file manual verification tool.

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?

The word 'Batch' implies this is for many files rather than one, which gives some usage context. But there is no explicit when-to-use guidance, no exclusions, and no named alternative for single-file verification.

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