Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Mayúsculas de nombres en español

es-name-case
Read-onlyIdempotent

Capitaliza nombres propios al estilo español, con partículas en minúscula (de, del, de la, y…), guiones y apóstrofos. 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: convertir a formato de título (case-title). 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: Capitalizes personal or place names in Spanish style, keeping particles lowercase (de, del, de la, y, e, los, las, da, van, von) except at the start, and handling hyphens and apostrophes. When: Spanish text, numbers or dates have to be handled by the written rules of Spanish instead of by approximation. Not for: capitalizing words as a title (case-title). Side effects: none (read-only, no network access, no stored state). [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
nameYesName (string; required; up to 500 chars).

Output Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / examples
      Added value: +[
+  "MARÍA DE LOS ÁNGELES GÓMEZ-RESTREPO"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Capitalizes personal or place names in Spanish style, keeping particles lowercase (de, del, de la, y, e, los, las, da, van, von) except at the start, and handling hyphens and apostrophes. When: Spanish text, numbers or dates have to be handled by the written rules of Spanish instead of by approximation. Not for: capitalizing words as a title (case-title). 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.6/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, so the 'sin efectos secundarios / determinista' sentence largely restates them. The genuinely additive content is the limits block (64 KB input, 1 s per call, 1 MB result), which no structured field conveys.

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 verb and the rule set, then cleanly separated into when / not-for / side effects / limits. Slightly redundant in that the side-effects and determinism sentences overlap with the annotations, but nothing is padded.

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 single-string transformer with an output schema, full annotation coverage and 100% param description coverage, the description supplies everything an agent needs: scope, exclusion, determinism, and operational limits.

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?

Only one parameter and schema coverage is 100%, so the baseline is 3. The description still adds real semantics the schema lacks: how particles (de, del, de la, y, e, da, van, von) are treated, that they stay lowercase except at the start, and how hyphens and apostrophes are handled.

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 ('Capitaliza') and resource ('nombres propios al estilo español') plus the exact rule set: particles lowercase, hyphens, apostrophes. It also explicitly sets itself apart from the sibling case-title, so an agent can discriminate 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?

Uses explicit 'Cuándo' and 'No para' markers, and names the alternative (case-title) that handles the title-case use case. The selection condition between the two tools is unambiguous.

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