Skip to main content
Glama

Create several deliveries

create_batch
Destructive

Up to 25 create_delivery payloads in one call.

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": {
      "deliveries": "<deliveries>"
    },
    "name": "create_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
deliveriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the risk profile is covered by structured data. The description adds the batch ceiling of 25 and the fact that each element is a create_delivery payload, which is useful context. It is silent on the behaviors that matter most for a batch write — partial failure handling, atomicity, and whether the response contains per-item results.

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?

A single eight-word sentence that front-loads the constraint (up to 25) and contains no filler. It is efficiently written, though the extreme terseness verges on under-specification rather than economy.

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 destructive, non-idempotent batch mutation with no output schema, the description is too thin — it omits atomicity, partial-failure semantics, and what the caller gets back per item. The only thing making it usable at all is the implicit reuse of create_delivery's payload contract, which is never made explicit as a contract.

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 0% and the items schema is an empty object with additionalProperties {}, so the description does real work by telling the agent each item is a create_delivery payload, resolving an otherwise opaque shape. Beyond that pointer it adds nothing about required fields per item, ordering, or how duplicates are treated.

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 identifies the resource (deliveries) and the batching scope (up to 25 payloads in one call), and by naming 'create_delivery payloads' it implicitly distinguishes itself from the single-item sibling. The explicit verb 'create' never appears, so an agent must infer that this writes rather than reads, but the intent is still recoverable.

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 guidance on when to prefer this over repeated create_delivery calls, no prerequisite or authorization notes, and no mention of when-not to use it. The only implied signal is the 25-item cap, which suggests batching for volume, but nothing is stated.

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.