Skip to main content
Glama

Write several things at once

pipeline_batch
Destructive

Write several things in ONE atomic call. Every item is validated first; if any item is invalid NOTHING is written and the response names which one; if all are valid they are written in a single transaction and you get exactly one acknowledgement per item, in input order. Nothing is ever partially applied or silently dropped. A retry with the same idempotency_key returns the first response and writes nothing.

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": {
      "items": "<items>"
    },
    "name": "pipeline_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesEach item is { op, ... } where op is post_card, message, answer, match or open.
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Strong disclosure beyond annotations: validation happens before any write, a failure names the offending item, nothing is partially applied or silently dropped, and one acknowledgement is returned per item in input order. The only friction is the idempotency claim: annotations set idempotentHint=false while the description says a retry with the same idempotency_key returns the first response and writes nothing — reconcilable only if the key is optional, which the description never states outright.

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 definition is front-loaded with the atomic-batch guarantee and proceeds in a logical order: validation, failure behavior, success behavior, retry behavior. It is dense but earns most of its space, with mild redundancy in 'Nothing is ever partially applied or silently dropped,' which restates the atomicity already asserted.

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?

With no output schema and only two parameters, the description covers everything an agent needs: atomicity, failure indication, per-item acknowledgement ordering, and retry semantics. The absence of an explicit note that idempotency_key is optional is a small gap but does not block correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and idempotency_key has no schema description at all, so the description carries real weight there by explaining that a retry with the same key returns the cached first response and performs no writes. For items it adds validation semantics (all-or-nothing, order of acknowledgements) rather than field-level detail, which is appropriate since the schema already enumerates the accepted op values.

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?

The description opens with a specific verb+resource and scope: 'Write several things in ONE atomic call,' and the schema-listed ops (post_card, message, answer, match, open) make clear it is the batched counterpart of the single-operation write siblings like pipeline_post_card. An agent can tell immediately this is the bulk-write path rather than a single-item one.

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?

Usage is implied by 'several things in ONE atomic call' and the all-or-nothing validation rule, which effectively signals 'use this when you need multiple writes to succeed together.' However, there is no explicit when-to-use/when-not guidance and no named alternative for the single-item case, leaving the agent to infer it.

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