Skip to main content
Glama

Batch records by row count

bpj_table_batches
Read-onlyIdempotent

Partition input records into fixed-size batches, retaining a shorter final batch.

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": {
      "rows": "<rows>",
      "size": "<size>"
    },
    "name": "bpj_table_batches"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
sizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 closed-world, so safety is fully covered. The description adds one genuine behavioral fact beyond them: the final batch is retained even when shorter than the batch size, which tells the agent no rows are dropped. It says nothing about output form (array of arrays vs. delimited) or how a 12,000-character input is handled.

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?

A single sentence with the core operation front-loaded and zero filler. Nothing in it is redundant, and it reads cleanly without preamble.

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?

For a simple two-parameter pure function with complete annotations and no output schema, this is close to sufficient. The remaining gaps are the serialization format of the input and the shape of the returned batches, which matter for correct invocation of a batching utility.

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%, so the description must compensate, but it only restates "records" and "fixed-size" without clarifying that rows is a JSON-encoded string (not a native array) or that size is bounded to 1–300. The critical detail that the input must be JSON text rather than structured data is left entirely to the schema title.

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 specific verb and resource: "Partition input records into fixed-size batches," which is precise enough that an agent knows exactly what transformation happens. It does not distinguish itself from look-alike siblings such as bpj_table_group_boundaries or bpj_table_group_cardinality, so an agent choosing among the many table tools gets no routing help.

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?

The description contains no when-to-use guidance, no preconditions, and no mention of any alternative tool. It never says when batching is the right operation versus grouping or row-numbering, leaving the agent to infer usage entirely from the name.

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.