Burs-IA Utils

Ordenar arreglo

array-sort

Read-onlyIdempotent

Ordena un arreglo de valores u objetos por una o más claves (orden estable, natural). Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: ordenar líneas con intercalación por idioma (lines-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: Sorts an array of values or objects by one or more keys (stable), ascending or descending, numbers before strings, with locale-aware natural string comparison. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: sorting lines with locale-aware collation (lines-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
`by`	No	Keys to sort by (empty: sort values) (array of string; optional; default []; up to 10 items).
`items`	Yes	Array (array; required).
`order`	No	Order (optional; one of: asc, desc; default "asc").	asc

Output Schema

Name	Required	Description	Default
`items`	No	any JSON value

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / items / examples

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

First observedNov 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further with concrete operational limits (64 KB input, 1 s per call, 1 MB result), determinism guarantee, and no-state/no-network confirmation. These are useful traits an agent cannot derive from the annotations alone.

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 core verb and behavior, and each sentence (when, not-for, side effects, determinism, limits) earns its place. However, the full ES/EN duplication roughly doubles the length for the same content, which slightly hurts conciseness.

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?

Output schema and annotations handle return format and safety profile, while the description covers scope, limits, ordering semantics, and determinism. Nothing an agent needs to invoke it correctly is missing.

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 semantic value beyond the schema: the 'stable' guarantee, 'numbers before strings', and 'locale-aware natural string comparison' clarify sort behavior. It doesn't add much on the `by`/`order` parameters themselves, which the schema already documents.

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 (sorts), resource (array of values or objects), and distinguishing behavior (stable, ascending/descending, numbers before strings, locale-aware natural comparison). It explicitly names the sibling it is not for (lines-sort), so the agent can tell it apart 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?

Explicit 'When' clause lists the concrete data shapes (JSON, CSV, YAML, XML, arrays) suited for it, and an explicit 'Not for' clause routes line-collation tasks to lines-sort. Both the positive and negative selection conditions are stated.

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

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?