Skip to main content
Glama

Decompress a batch packet

unpack_batch
Read-onlyIdempotent

Unpack a batch packet made by pack_batch (or by the /api/v1/pack-batch endpoint) back into the exact original list of messages, in order. REQUIRES A KEY. Not for a packet made by the single-message pack endpoint — that is a different format and this will reject it.

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": {
      "packet_b64": "<packet_b64>"
    },
    "name": "unpack_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoOptional. A label for audit/metrics.
packet_b64YesThe packet_b64 returned by pack_batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds real value: an authentication requirement ('REQUIRES A KEY'), the rejection behavior on wrong-format input, and a round-trip guarantee that output order matches the original.

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?

Three short sentences with zero filler, and the core purpose plus the producer tool are front-loaded. The key requirement and the format exclusion follow in priority order without repetition.

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

Completeness5/5

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

For a two-parameter tool with no output schema, the description supplies what is missing: the return value (the exact original message list, in order), the auth prerequisite, and the failure mode for wrong input. Nothing an agent needs to invoke it correctly is absent.

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 coverage is 100%, so both parameters are already documented in structured fields. The description only reinforces that packet_b64 comes from pack_batch and says nothing about agent_id, so it adds no meaning beyond the schema. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('Unpack a batch packet ... back into the exact original list of messages, in order') and names the producing tool, pack_batch. It also explicitly distinguishes itself from the single-message pack format, so an agent can tell which unpack path applies without inspecting schemas.

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

Usage Guidelines4/5

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

Gives a clear when-to-use pairing (packets made by pack_batch or the /api/v1/pack-batch endpoint) and an explicit when-not-to-use case (single-message pack output, which it will reject). It stops short of naming the correct tool for that excluded format, so the agent knows to look elsewhere but not where.

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.