Burs-IA Utils

Medias aritmética, geométrica y armónica

stats-means

Read-onlyIdempotent

Calcula media aritmética, geométrica, armónica, cuadrática y ponderada. Cuándo: un resultado numérico tiene que ser exacto o reproducible y no estimado. No para: calcular la estadística descriptiva de una lista de números (stats-describe). 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 arithmetic, geometric and harmonic means (the latter two only for positive values), root mean square, and a weighted mean when weights are supplied. When: a numeric result has to be exact or reproducible instead of estimated. Not for: computing descriptive statistics of a list of numbers (stats-describe). 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
`values`	Yes	Numbers (array of number; required; at least 1 items).
`weights`	No	Optional weights, same length (array of number; optional).

Output Schema

Name	Required	Description	Default
`harmonic`	No
`weighted`	No
`geometric`	No
`quadratic`	No
`arithmetic`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / values / examples
```
Added value: +[
+  [
+    1,
+    2,
+    4
+  ]
+]
```
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, idempotentHint, openWorldHint=false and destructiveHint=false, and the description restates those. The added value is real though: hard limits (64 KB input, 1 s per call, 1 MB result) and the domain rule that geometric/harmonic require positive values — neither is discoverable from the schema or annotations.

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, then labeled sections for usage, side effects, determinism and limits — highly scannable. The bilingual ES/EN duplication roughly doubles the length, and the side-effects/determinism sentences largely repeat the annotations, costing some efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-value explanation is rightly omitted, and the limits plus positivity constraint cover the main failure modes. The only gap is error behavior for mismatched weights or non-positive inputs to geometric/harmonic means, which an agent must infer.

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; the description exceeds it by explaining that weights trigger the weighted-mean mode and that values must be positive for the geometric/harmonic variants — behavioral meaning the schema's 'array of number' text does not convey. It does not state what happens on a weights/values length mismatch, which keeps it below 5.

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?

The description names the exact resource and enumerates the operations: arithmetic, geometric, harmonic, quadratic (RMS) and weighted means, plus the constraint that geometric/harmonic apply only to positive values. This is unambiguously distinguishable from stats-describe and stats-correlation in the sibling list.

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 (a numeric result must be exact or reproducible, not estimated) and an explicit 'Not for:' clause naming the sibling stats-describe for descriptive statistics. This is the when/when-not/alternative triad in compact form.

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?