Burs-IA Utils

Construir data: URI

data-uri-build

Read-onlyIdempotent

Construye una URI data: (RFC 2397) desde texto o bytes y un tipo MIME. Cuándo: hay que convertir bytes o texto a esta codificación, o desde ella, con exactitud y sin adivinar. No para: analizar una URI data (data-uri-parse). 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: Builds an RFC 2397 data: URI from text or base64 bytes and a MIME type, using base64 or percent-encoding. When: bytes or text have to be converted to or from this encoding exactly, without guessing. Not for: parsing an RFC 2397 data: URI into MIME type, parameters, base64 flag, byte size and content (data-uri-parse). 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.

Input Schema

Name	Required	Description	Default
`data`	Yes	Content (string; required).
`mime`	No	MIME type (string; optional; default "text/plain"; up to 200 chars; pattern ^[\w.+-]+/[\w.+-]+(;\s[\w.+-]+=[\w.+-]+)$).	text/plain
`base64`	No	Use base64 (boolean; optional; default true).
`input_encoding`	No	Encoding of data (optional; one of: utf8, base64; default "utf8").	utf8

Output Schema

Name	Required	Description	Default
`uri`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / data / examples
```
Added value: +[
+  "hi"
+]
```
First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses determinism, absence of network/state, and concrete limits (64 KB JSON input, 1 s per call, 1 MB result) that no structured field conveys. Annotations already cover read-only/idempotent, and the description adds operational constraints rather than contradicting them.

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

Conciseness3/5

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

Front-loaded and clearly labeled (When / Not for / Side effects / Deterministic / Limits), but the entire body is duplicated in Spanish and English, roughly doubling length with no added information. A single-language version would be tight.

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 4 parameters, full schema coverage, and an output schema present, the description covers everything an agent needs: what it produces, when to choose it over the sibling, safety profile, determinism, and size/time limits.

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 coverage is 100%, so the baseline is 3. The description adds only light semantics over the schema — 'text or base64 bytes' maps to input_encoding and 'base64 or percent-encoding' hints at the base64 flag — but gives no per-parameter detail the schema lacks.

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 (builds), resource (an RFC 2397 data: URI) and inputs (text or base64 bytes plus a MIME type, base64 or percent-encoding). It explicitly names the inverse sibling (data-uri-parse), so an agent can distinguish the two without opening schemas.

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?

Provides an explicit 'When' clause (converting bytes/text to or from this encoding exactly, without guessing) and an explicit 'Not for' clause routing to data-uri-parse. The alternative and the condition that selects it are both named.

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?