Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Separar en sílabas

es-syllabify
Read-onlyIdempotent

Separa palabras en sílabas según las reglas ortográficas de la RAE: diptongos, triptongos, hiatos (í/ú con tilde), grupos inseparables (pl, br, tr…), ch/ll/rr y la u muda de que/gui. Las divisiones por prefijo (sub-, des-) pueden variar. Cuándo: hay que tratar texto, números o fechas en español según las reglas escritas del idioma y no por aproximación. No para: analizar una palabra (es-stress). 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: Splits Spanish words into syllables with the RAE orthographic rules: diphthongs, triphthongs, hiatus (accented í/ú), inseparable clusters (pl, br, tr…), ch/ll/rr and silent u in que/gui. Prefix-based splits (sub-, des-) may differ. When: Spanish text, numbers or dates have to be handled by the written rules of Spanish instead of by approximation. [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
textYesOne or more Spanish words (string; required; up to 20000 chars).

Output Schema

NameRequiredDescriptionDefault
wordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / text / examples
      Added value: +[
+  "murciélago"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Splits Spanish words into syllables with the RAE orthographic rules: diphthongs, triphthongs, hiatus (accented í/ú), inseparable clusters (pl, br, tr…), ch/ll/rr and silent u in que/gui. Prefix-based splits (sub-, des-) may differ. When: Spanish text, numbers or dates have to be handled by the written rules of Spanish instead of by approximation. Not for: analyzing a Spanish word (es-stress). 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."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds genuine context beyond annotations: an explicit time budget (1 s/call), result size cap (1 MB), input size limit (64 KB) and the orthographic caveat that prefix-based splits may differ. It does partly restate annotations ('solo lectura, sin red, sin estado guardado' / 'Determinista' mirror readOnlyHint, openWorldHint=false, idempotentHint), which caps the score below 5.

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 operation, then clearly labeled blocks (Cuándo / No para / Efectos / Determinista / Límites) that make scanning easy. Slight redundancy from running the content in both Spanish and English before deferring to inputSchema.description for the full EN.

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?

With annotations, a fully documented single parameter and an output schema present, nothing an agent needs is missing: scope, exclusion, determinism, resource limits and the prefix-split edge case are all stated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single required parameter with 100% schema description coverage and an example ('murciélago'), so the schema already carries parameter meaning. The description adds no format or edge-case detail about the 'text' field beyond what the schema states, so the baseline 3 applies.

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?

Starts with a specific verb+resource ('Separa palabras en sílabas') and immediately enumerates the rules it applies (diptongos, triptongos, hiatos, grupos inseparables, ch/ll/rr, u muda). It also explicitly contrasts with the sibling es-stress, so an agent can distinguish it without opening any 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?

Has explicit 'Cuándo:' (Spanish text/numbers/dates must follow written orthographic rules, not approximation) and 'No para:' routing the word-analysis case to es-stress. The prefix-split caveat (sub-, des-) tells the agent when output may legitimately vary.

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 toolsInspect
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