Burs-IA Utils

Dividir arreglo en bloques

array-chunk

Read-onlyIdempotent

Divide un arreglo en bloques de tamaño fijo, p. ej. para enviar en lotes. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: ordenar un arreglo de valores u objetos por una o más claves (array-sort). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Splits an array into consecutive chunks of a given size (last chunk may be shorter), e.g. for batching API calls. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: sorting an array of values or objects by one or more keys (array-sort). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB.

Input Schema

Name	Required	Description	Default
`size`	Yes	Chunk size (integer; required; min 1; max 100000).
`items`	Yes	Array (array; required).

Output Schema

Name	Required	Description	Default
`count`	No
`chunks`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / items / examples
```
Added value: +[
+  [
+    1,
+    2,
+    3,
+    4,
+    5
+  ]
+]
```
- addedInput schema / properties / size / examples
```
Added value: +[
+  2
+]
```
First observedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, idempotent and closed-world, but the description adds real value beyond them: deterministic output, no stored state, and concrete limits (64 KB input, 1 s per call, 1 MB result). It does not repeat the annotation fields verbatim, so no contradiction.

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 core action is front-loaded and the labeled sections (Cuándo / No para / Efectos / Límites) make scanning easy. It is somewhat verbose and the full bilingual duplication doubles length, but every section carries information rather than padding.

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?

For a two-parameter, deterministic utility, the description covers purpose, alternatives, side effects and resource limits, and an output schema exists so return values need not be explained. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so both parameters are already documented in the schema; the baseline is 3. The description's note that the last chunk may be shorter adds marginal semantic detail about the size parameter, but it doesn't explain formats or edge cases further.

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?

States a specific verb+resource ('Divide un arreglo en bloques de tamaño fijo') with the concrete purpose of batching, and explicitly names the sibling it is not (array-sort). An agent can distinguish it from other array tools without opening the schema.

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?

Provides an explicit 'Not for' clause routing the agent to array-sort, which is strong. The positive 'Cuándo' guidance is broad ('transform, compare or check structured data exactly') and doesn't discriminate against other array siblings like array-flatten or array-group-by, so it falls short of a 5.

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

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?