Burs-IA Utils

Normalizar URL

url-normalize

Read-onlyIdempotent

Normaliza una URL para comparar o deduplicar: minúsculas, sin puerto por defecto, sin parámetros de seguimiento, etc. 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: construir una URL desde una base, segmentos de ruta y parámetros de consulta (url-build). 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: Normalizes a URL for comparison or deduplication: lowercase scheme/host, drop default port, resolve dot segments, optionally sort query, drop tracking parameters (utm_*, gclid, fbclid…), fragment and trailing slash. 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

Name	Required	Description
`url`	Yes	URL (string; required; up to 8192 chars).
`remove_www`	No	Strip leading www (boolean; optional; default false).
`sort_query`	No	Sort query parameters (boolean; optional; default true).
`remove_fragment`	No	Remove #fragment (boolean; optional; default true).
`remove_tracking`	No	Remove utm_* and click IDs (boolean; optional; default true).
`remove_trailing_slash`	No	Remove trailing slash from path (boolean; optional; default false).

Output Schema

Name	Required	Description	Default
`url`	No
`removed_params`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / url / examples

Added value: +[
+  "HTTPS://WWW.Example.com:443/a/./b/../c?utm_source=x&b=2&a=1#sec"
+]

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Normalizes a URL for comparison or deduplication: lowercase scheme/host, drop default port, resolve dot segments, optionally sort query, drop tracking parameters (utm_*, gclid, fbclid…), fragment and trailing slash. 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: building a URL from a base, optional path segments (url-build). 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."

First observedNov 1, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, but the description still adds real value: no network access, no stored state, deterministic output, and hard limits (64 KB input, 1 s per call, 1 MB result). Only the output schema's own richness limits further credit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is duplicated in full in Spanish and English, and then points to 'inputSchema.description' for a third copy, so the same content appears three times in one call path. The generic 'Cuándo' enumeration and the limits block also occupy space disproportionate to a single-URL transform, though the first sentence is well front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given annotations plus a complete schema and an output schema, the description covers the remaining unknowns an agent needs: side effects, determinism, resource limits, and the non-recommended sibling. Return-value explanation is correctly omitted.

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?

Schema description coverage is 100% and every one of the 6 parameters is documented with type and default in the schema. The description's prose ('sort query', 'drop tracking parameters (utm_*, gclid, fbclid…)', 'fragment and trailing slash') restates those flags without adding format or interaction detail, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb (normalize) and resource (URL) plus the goal (comparison/deduplication), and enumerates the concrete transformations. It names the sibling it is not for (url-build), but the later 'Cuándo' clause also says it is for 'construir ... una URL', which muddies the very distinction it just drew.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicit dual structure: 'Cuándo' for when and 'No para: ... (url-build)' for the alternative, which is exactly what an agent needs to route correctly. However, the 'Cuándo' list (HTTP headers, tokens, versions, IP ranges, HTML/Markdown, agent files) is boilerplate that does not actually apply to URL normalization and weakens the 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 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?