Skip to main content
Glama

binary-forensics

archive_join_and_verify

Stitch split multi-part archive chunks, detect magic file header, compute & verify SHA-256 checksum, and peek ZIP Central Directory entries.

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

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo
outputPathNo
partsBase64No
expectedSha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It lists stitching, verification, and ZIP inspection, but does not disclose side effects such as writing outputPath, required input combinations, permissions, error behavior, or return shape.

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?

The single sentence is front-loaded and free of filler. It is dense but appropriately concise, though the action list could be more structured for a multi-step tool.

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?

For a five-parameter, multi-operation tool with no annotations and no output schema, the description omits input relationships, side effects, and output details. It is not complete enough for reliable invocation by an agent.

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 coverage is 0% across five parameters. The description indirectly maps to partsBase64 and expectedSha256, but leaves filePath, base64Data, outputPath, requiredness, and one-of input semantics unexplained.

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?

The description names concrete actions and a specific resource: stitching split multi-part archive chunks, verifying SHA-256, and peeking ZIP central directory entries. It is clearly archive-specific and distinguishable from the listed siblings, though it does not explicitly compare alternatives.

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 explicit when-to-use, when-not-to-use, or alternative-selection guidance. An agent can infer that this is for split archives and checksum verification, but the description leaves that inference to the reader.

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