Burs-IA Utils

Quitar duplicados de un arreglo

array-dedupe

Read-onlyIdempotent

Elimina elementos duplicados (igualdad profunda) o por clave, conservando el primero. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: agrupar textos casi duplicados (dedupe-similar). 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: Removes duplicate items (deep equality via canonical JSON) or items with a duplicate key, keeping the first occurrence and original order. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: grouping near-duplicate strings (dedupe-similar). 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
`by`	No	Object key (dotted path allowed) to compare by (string; optional; up to 500 chars).
`items`	Yes	Array (array; required).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / items / examples

Added value: +[
+  [
+    1,
+    2,
+    1,
+    {
+      "a": 1
+    },
+    {
+      "a": 1
+    }
+  ]
+]

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so the safety profile is covered. The description still adds non-redundant operational context: hard limits (64 KB input, 1 s per call, 1 MB result), deterministic output, and that first-occurrence order is preserved. It does not add anything contradictory; determinism partly restates idempotentHint, which keeps it just short of 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded and well segmented (purpose, when, not-for, side effects, determinism, limits), but the entire block is duplicated in Spanish and English, roughly doubling length with zero added information. The English half alone would merit a 5; the duplication is pure structural cost.

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 2-parameter, read-only array tool with an output schema, the description covers everything the agent needs: purpose, sibling boundary, purity guarantees, determinism, and hard size/time limits. Output formatting is covered by the output schema, so its absence from the description is not a gap.

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 would be 3. The description earns above baseline by explaining the comparison semantics that the schema cannot: default is deep equality via canonical JSON, while `by` switches to key-based comparison — that meaningfully disambiguates the optional `by` parameter, though it adds no new information about the `items` shape.

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 ("Elimina elementos duplicados") plus the two comparison modes (deep equality / by key) and the retention rule (keeps first occurrence, preserves order). It explicitly contrasts itself with the nearest sibling, dedupe-similar, so an agent can select between them without opening either schema.

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?

Uses an explicit "Cuándo:/When:" clause naming the data shapes it is meant for (JSON, CSV, YAML, XML, arrays) and an explicit "No para:/Not for:" clause routing near-duplicate string grouping to dedupe-similar. Both the include and the exclude condition are stated, which is the top of the scale.

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?