Skip to main content
Glama
Sign In

Burs-IA Utils

by io.github.soyeladice-svg
OverviewDiscussionsAdmin

Validar sintaxis de dominio

domain-syntax-validate
Read-onlyIdempotent

Verifica la sintaxis de un nombre de dominio (etiquetas, longitudes, TLD), sin consultar DNS. Cuándo: hay que leer, construir o revisar con exactitud una URL, una cabecera HTTP, un token, una versión, un rango de IP, un documento HTML o Markdown o un archivo para agentes. No para: verificar solo la SINTAXIS de un correo (email-syntax-validate). 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: Checks hostname syntax (RFC 1035/1123 labels, total ≤ 253, label ≤ 63, alphabetic or xn-- TLD), detects IDN/punycode labels and IP literals. Does not query DNS and does not use the Public Suffix List. When: a URL, HTTP header, token, version string, IP range, HTML or Markdown document or agent-readiness file has to be parsed, built or checked exactly. [EN completo / full EN: inputSchema.description]

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name (string; required; up to 300 chars).

Output Schema

NameRequiredDescriptionDefault
idnNo
validNo
labelsNo
reasonsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain / examples
      Added value: +[
+  "api.burs-ia.com"
+]
  2. Changed1 schema field changed
    • addedInput schema / description
      Added value: +"EN: Checks hostname syntax (RFC 1035/1123 labels, total ≤ 253, label ≤ 63, alphabetic or xn-- TLD), detects IDN/punycode labels and IP literals. Does not query DNS and does not use the Public Suffix List. When: a URL, HTTP header, token, version string, IP range, HTML or Markdown document or agent-readiness file has to be parsed, built or checked exactly. Not for: checking email address SYNTAX only (email-syntax-validate). 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, openWorldHint=false and idempotentHint, yet the description still contributes genuinely new facts: no DNS query, no Public Suffix List, and hard limits (64 KB input, 1 s, 1 MB result). Determinism restates idempotentHint somewhat, which is the only redundancy.

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 purpose then structured into labeled blocks (Cuándo / No para / Efectos / Límites) that scan quickly. It loses a point for restating the full EN text that also lives in inputSchema.description, creating near-duplicate content.

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?

An output schema exists so return values need no explanation, and the description covers the remaining gaps: validation rules, offline behavior, determinism and size/time limits. Nothing needed to call a single-parameter validator 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?

Only one parameter at 100% schema coverage, so the baseline is 3; the description nevertheless adds semantic constraints beyond the schema — total ≤ 253, label ≤ 63, alphabetic or xn-- TLD, IDN/punycode and IP-literal detection — which tell the agent what input will actually pass.

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 ("Verifica la sintaxis de un nombre de dominio") and immediately scopes it ("etiquetas, longitudes, TLD, sin consultar DNS"). The EN paragraph adds the exact RFC basis (1035/1123) and thresholds, so an agent can distinguish it from URL/IP/email validators 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?

Uses explicit "Cuándo" / "No para" blocks and names the alternative that must be used instead for email syntax (email-syntax-validate). The exclusion is unambiguous, which is the rare case where alternatives are stated outright rather than implied.

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