Burs-IA Utils

Contar apariciones

count-occurrences

Read-onlyIdempotent

Cuenta apariciones de una subcadena y devuelve sus posiciones. Cuándo: hay que transformar, comparar o medir un texto con exactitud y no por aproximación. No para: contar la frecuencia de palabras en un texto (word-frequency). 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: Counts non-overlapping (or overlapping) occurrences of a substring, optionally case-insensitive, and returns their indices (first 1,000). When: text has to be transformed, compared or measured exactly instead of approximated. Not for: counting word frequencies in text (word-frequency). 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
`text`	Yes	Input text (string; required).
`substring`	Yes	Substring (string; required; at least 1 chars; up to 1000 chars).
`overlapping`	No	Count overlapping matches (boolean; optional; default false).
`case_sensitive`	No	Case sensitive (boolean; optional; default true).

Output Schema

Name	Required	Description	Default
`count`	No
`indices`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / substring / examples
```
Added value: +[
+  "ana"
+]
```
- addedInput schema / properties / text / examples
```
Added value: +[
+  "banana"
+]
```
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/closed-world, but the description adds concrete operational context beyond them: no network, no stored state, determinism, and hard limits (64 KB input, 1 s per call, 1 MB result). This is exactly the extra context the annotations cannot convey.

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 action, then organized into labeled sections (When / Not for / Side effects / Deterministic / Limits). The bilingual duplication makes it longer than strictly necessary, but every sentence carries information.

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 4-parameter read-only tool with an output schema, the description covers purpose, alternatives, side effects, determinism, and resource limits. 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 meaning beyond the schema by explaining that matches are non-overlapping by default (overlapping optional), case-insensitive mode is available, and only the first 1,000 indices are returned. That clarifies the two boolean flags' effect on results.

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 ('Cuenta apariciones de una subcadena y devuelve sus posiciones') and explicitly names the sibling it is not for (word-frequency), so an agent can distinguish it 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 Guidelines5/5

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

Provides an explicit 'Cuándo' condition (exact text transformation/comparison/measurement rather than approximation) and an explicit 'No para' exclusion pointing to word-frequency. Both when-to-use and when-not-to-use are covered.

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?