Burs-IA Utils

Operaciones de conjuntos con arreglos

array-set-ops

Read-onlyIdempotent

Calcula unión, intersección, diferencia o diferencia simétrica de dos arreglos. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: eliminar elementos duplicados (array-dedupe). 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: Computes union, intersection, difference (a−b) or symmetric difference of two arrays using deep equality, preserving first-seen order. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: removing duplicate items (array-dedupe). 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
`a`	Yes	First array (array; required).
`b`	Yes	Second array (array; required).
`operation`	Yes	Operation (required; one of: union, intersection, difference, symmetric_difference).

Output Schema

Name	Required	Description	Default
`count`	No
`items`	No	any JSON value

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026
- addedInput schema / properties / a / examples
```
Added value: +[
+  [
+    1,
+    2,
+    3
+  ]
+]
```
- addedInput schema / properties / b / examples
```
Added value: +[
+  [
+    2,
+    3,
+    4
+  ]
+]
```
- addedInput schema / properties / operation / examples
```
Added value: +[
+  "intersection"
+]
```
First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the description only needs incremental detail — and it delivers: hard limits (64 KB JSON input, 1 s per call, 1 MB result), determinism, and the deep-equality/order-preservation semantics of the comparison. A 4 rather than 5 because it does not say what happens when a limit is exceeded (truncation vs. error).

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?

Front-loaded with the operation list and organized into labeled clauses (When / Not for / Side effects / Deterministic / Limits), which is easy to scan. Slightly penalized for full Spanish/English duplication, which doubles length for the same content.

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?

An output schema exists, so return values need no prose. The description covers the operation set, comparison semantics, safety profile, determinism, and resource limits — everything needed to invoke correctly and predict behavior.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot: elements are compared by deep equality, output order follows first-seen order, and difference is directional (a−b). That last point matters because the enum alone lists 'difference' without stating orientation.

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 and resource, enumerates the four supported operations (union, intersection, difference, symmetric difference), and specifies deep equality plus first-seen order preservation. It explicitly names the sibling array-dedupe as the thing it is not, so an agent can separate the two without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Has explicit 'Cuándo/When' and 'No para/Not for' clauses, and names the alternative tool (array-dedupe) with the condition that selects it. Nothing about when to reach for this versus a sibling is left to inference.

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?