Burs-IA Utils

Subir versión semántica

semver-bump

Read-onlyIdempotent

Incrementa una versión SemVer (major, minor, patch o prerelease con identificador opcional). 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: validar y analizar una versión SemVer 2.0.0 en mayor, menor, parche, prerelease y build (semver-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: Increments a SemVer version: major, minor, patch, premajor, preminor, prepatch or prerelease (with an optional identifier like beta or rc), following npm semver semantics. 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
`release`	Yes	Release type (required; one of: major, minor, patch, premajor, preminor, prepatch, prerelease).
`version`	Yes	Semantic version, e.g. 1.2.3-beta.1 (string; required; up to 256 chars).
`identifier`	No	Prerelease identifier, e.g. beta (string; optional; up to 30 chars; pattern ^[0-9A-Za-z-]+$).

Output Schema

Name	Required	Description	Default
`version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / release / examples
```
Added value: +[
+  "minor"
+]
```
- addedInput schema / properties / version / examples
```
Added value: +[
+  "1.2.3"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Increments a SemVer version: major, minor, patch, premajor, preminor, prepatch or prerelease (with an optional identifier like beta or rc), following npm semver semantics. 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: validating and parsing a SemVer 2.0.0 string (semver-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."

First observedNov 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld=false and destructive=false, and the description still adds concrete value: explicit limits (64 KB input, 1 s per call, 1 MB result) and a determinism guarantee. The side-effects line largely restates the annotations, so it is additive rather than fully independent.

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?

The operative sentences are well front-loaded, but the 'When' boilerplate about URLs, HTTP headers, tokens, IP ranges and HTML/Markdown documents is irrelevant to version bumping and appears to be reused template text, wasting space and inviting misapplication.

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?

With an output schema, full parameter coverage and rich annotations, the description plus structured fields are sufficient to call the tool correctly. The remaining gap is the misleading generic usage clause, not missing invocation-critical information.

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% and the enum for 'release' is fully documented in the schema, so the baseline is 3. The description restates the same release list and mentions the optional identifier (beta/rc), adding marginal meaning beyond what the schema already provides.

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 EN text gives a specific verb and resource ('Increments a SemVer version') and enumerates the release modes plus npm semver semantics, which lets an agent separate it from siblings like semver-compare or semver-sort. The clarity is diluted by the boilerplate 'When' clause listing URLs, IP ranges and HTML documents, which does not describe what this tool does.

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?

It explicitly names the alternative: 'No para: validar y analizar una versión SemVer 2.0.0 ... (semver-parse)', which is exactly the kind of routing signal that separates bumping from parsing. The positive 'Cuándo' clause, however, is generic copy that mentions unrelated artifact types, so the when-to-use half is weaker than the when-not half.

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?