Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Buscar idioma ISO 639-1

iso-language-lookup
Read-onlyIdempotent

Busca códigos de idioma ISO 639-1 de dos letras por código o por nombre en español o inglés (sin importar tildes, coincidencia parcial). Nombres del CLDR de Unicode incluido en Node.js. Cuándo: hay que transformar, comparar o revisar con exactitud datos estructurados (JSON, CSV, YAML, XML, arreglos). No para: buscar países ISO 3166-1 alfa-2 por código o por nombre en español o inglés (iso-country-lookup). 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: Looks up ISO 639-1 two-letter language codes by code or by name in Spanish or English (accent-insensitive, partial match). Names come from the Unicode CLDR data bundled with Node.js. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (integer; optional; default 10; min 1; max 50).
queryYesCode (qu) or name (quechua, Spanish…) (string; required; at least 1 chars; up to 80 chars).

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNo
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / examples
      Added value: +[
+  "quechua"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Looks up ISO 639-1 two-letter language codes by code or by name in Spanish or English (accent-insensitive, partial match). Names come from the Unicode CLDR data bundled with Node.js. When: structured data (JSON, CSV, YAML, XML, arrays) has to be transformed, compared or checked exactly. Not for: looking up ISO 3166-1 alpha-2 countries by code or by name in Spanish or English (iso-country-lookup). 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 cover read-only, no network/open world, idempotent, and non-destructive behavior, but the description adds concrete operational limits: 64 KB input, 1 second per call, and 1 MB result. It also states deterministic behavior and no stored state, though some of that repeats annotation hints.

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?

The description is front-loaded with purpose, usage, exclusion, side effects, and limits, so it is easy to scan. However, the bilingual format repeats the same content in Spanish and English, which adds length beyond what is strictly necessary.

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 simple lookup tool with a complete input schema, rich annotations, and an output schema, the description covers purpose, alternatives, behavior, determinism, and limits. Nothing important for correct invocation appears 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 schema already documents both parameters. The description adds useful semantic detail beyond the schema: query accepts a code or name, works in Spanish or English, is accent-insensitive, supports partial matching, and uses Unicode CLDR data bundled with Node.js.

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 states a specific verb and resource: looking up ISO 639-1 two-letter language codes by code or by name in Spanish or English. It also explicitly distinguishes this from the sibling iso-country-lookup, so an agent can select it 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?

It gives explicit 'Cuándo' guidance about transforming, comparing, or checking structured data exactly, and a clear 'No para' exclusion pointing to iso-country-lookup for ISO 3166-1 alpha-2 country lookups. This is close to ideal routing guidance.

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