Skip to main content
Glama

batch_list

Read-onlyIdempotent

Find durable batches in a resumed project with compact counts, controls, costs, and batch_get links. Follow next_offset to page through results.

Instructions

Find durable batches in a resumed project. Return compact counts, controls, costs and batch_get links; follow next_offset for more.

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": {
      "task_id": "<task_id>"
    },
    "name": "batch_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is fully covered by structured data. The description adds genuine value by describing the response shape (compact counts, controls, costs, batch_get links) and the offset-based pagination loop. It stops short of noting default page size or ordering, which is the remaining behavioral gap.

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?

Two tight sentences with the core action front-loaded and pagination guidance placed after the return-value summary. Nearly every clause earns its place; a short gloss on "durable" or "resumed project" would have cost nothing and removed ambiguity.

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

Completeness3/5

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

The presence of an output schema means return values need not be explained, making the payload summary a bonus rather than a requirement. However, for a three-parameter tool with zero schema description coverage, the description leaves the most call-critical details (page size, task_id meaning) unaddressed, so it is only minimally adequate.

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 description coverage is 0% for three parameters, so the description carries the full burden and mostly fails it: limit, offset and task_id are never explained, and only offset is indirectly implied by "next_offset." The word "links" hints that results can be followed up via batch_get, but nothing clarifies task_id scoping or that limit defaults to 20.

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?

States a concrete verb and resource: "Find durable batches in a resumed project," and signals the return payload (counts, controls, costs, batch_get links). An agent can infer this is the listing counterpart to batch_get, though the qualifiers "durable" and "resumed project" are unexplained jargon that leave scope slightly fuzzy.

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?

No explicit when-to-use or when-not-to-use guidance relative to siblings like batch_get, batch_control, or task_list. The only operational guidance is "follow next_offset for more," which is pagination mechanics rather than tool selection, so the agent must infer the choice from the name alone.

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