Skip to main content
Glama

Meta Council

by com.meta-council
OverviewDiscussionsAdmin

Ticket Batch Create

ticket_batch_create
Idempotent

Preview or idempotently commit one atomic owner-private batch of structured tickets and nested subtickets. Preview is non-mutating and returns the normalized commit payload, exact preview_token, and deterministic predicted IDs as JSON. Commit requires that exact token: combine commit_payload with mode=commit, the caller-held idempotency_key, and preview_token. It returns the same IDs plus replay status. A caller-stable visible-ASCII idempotency_key is always required. MCP authorship is stamped by the server; callers cannot spoof it. Nested subtickets are bounded and validated by the ticket handler before any write. This never executes, sends, publishes, deletes, or mutates an external provider.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
ticketsYes
parent_idNo
preview_tokenNoExact preview_token returned by preview mode.
idempotency_keyYesCaller-stable visible-ASCII key. Reuse only for the exact same operation and payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null
  2. Changed2 schema fields changed
    • changedInput schema / properties / tickets / items / properties / status / description
      Previous value: -"Terminal task states are allowed; a node inferred as an epic from effort='epic' cannot start done."New value: +"Terminal task states are allowed; an explicit or legacy-inferred epic cannot start done."
    • addedInput schema / properties / tickets / items / properties / ticket_type
      Added value: +{
+  "description": "Immutable ticket kind. When omitted, legacy effort='epic' inference remains supported.",
+  "enum": [
+    "task",
+    "epic",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / tickets / items / properties / status / description
      Added value: +"Terminal task states are allowed; a node inferred as an epic from effort='epic' cannot start done."
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) by explaining the preview/commit distinction, the requirement for an exact preview_token, the atomic batch guarantee, validation of nested subtickets before any write, and the explicit guarantee that it 'never executes, sends, publishes, deletes, or mutates an external provider.' It also adds server-side authorship stamping and non-spoofability. No contradiction with annotations.

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?

The description is concise yet information-dense, using clear sentence boundaries. It front-loads the core purpose, then details the preview/commit flow, constraints, and safety guarantees in a logical order. Every sentence contributes operational value with no redundant phrasing.

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?

Given the complexity (preview/commit modes, nested subtickets, idempotency, atomicity) and no output schema, the description provides sufficient operational context: what preview returns, what commit requires, how idempotency works, and what side effects are excluded. It covers the essential behaviors an agent needs to invoke the tool correctly, and the schema covers parameter constraints.

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?

With only 40% schema description coverage, the description compensates by explaining the roles of mode ('combine commit_payload with mode=commit'), preview_token ('exact preview_token'), and idempotency_key ('caller-stable visible-ASCII'). It also clarifies the relationship between preview and commit parameters. However, it does not elaborate on the 'tickets' array structure or 'parent_id', though those are somewhat self-evident from the schema.

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 precise verb-resource pairing: 'Preview or idempotently commit one atomic owner-private batch of structured tickets and nested subtickets.' It clearly distinguishes itself from single-ticket creation tools like ticket_create via the 'batch' and 'preview or commit' framing, and the two modes are explicitly defined.

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?

The description provides clear context for when to use the tool: for atomic batch operations requiring preview-before-commit with an idempotency key. It explains the two-step workflow (preview then commit with exact token), which acts as usage guidance. However, it does not explicitly contrast with alternatives like ticket_create or ticket_plan, nor state 'use this when batch > 1' – so exclusions are left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Meta Council toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources