Burs-IA Utils

Convertir salario por periodo

salary-convert

Read-onlyIdempotent

Convierte salarios entre hora, día, semana, quincena, mes y año con horas y semanas configurables. Cuándo: un cálculo de dinero, impuestos o matemática financiera tiene que ser exacto y reproducible (redondeo, centavos, tasas). No para: convertir tasas entre efectiva anual (interest-rate-convert). 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: Converts pay between hourly, daily, weekly, biweekly, monthly and annual figures using configurable hours per week, days per week and weeks per year. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: converting interest rates between effective annual (interest-rate-convert). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description
`amount`	Yes	Pay amount (number; required; min 0; max 1000000000000).
`period`	Yes	Period of amount (required; one of: hourly, daily, weekly, biweekly, monthly, annual).
`days_per_week`	No	Workdays per week (number; optional; default 5; > 0; max 7).
`hours_per_week`	No	Hours per week (number; optional; default 40; > 0; max 168).
`weeks_per_year`	No	Paid weeks per year (number; optional; default 52; > 0; max 53).

Output Schema

Name	Required	Description	Default
`daily`	No
`annual`	No
`hourly`	No
`weekly`	No
`monthly`	No
`biweekly`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / amount / examples
```
Added value: +[
+  25
+]
```
- addedInput schema / properties / period / examples
```
Added value: +[
+  "hourly"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Converts pay between hourly, daily, weekly, biweekly, monthly and annual figures using configurable hours per week, days per week and weeks per year. When: a money, tax or financial-math result has to be exact and reproducible (rounding, cents, rates). Not for: converting interest rates between effective annual (interest-rate-convert). 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

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'sin red, sin estado guardado' largely restates them. The description still adds genuinely new facts the annotations don't carry: full determinism and concrete operational limits (64 KB input, 1 s per call, 1 MB output), which matter for an exact-math tool.

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 organized as When / Not for / Side effects / Deterministic / Limits, so scanning is easy. It is somewhat verbose by carrying full Spanish and English text that is duplicated again in the schema description, which costs a point.

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, annotations cover the safety profile, all five parameters are documented, and the description adds determinism and size/time limits. Nothing an agent needs to invoke this correctly is missing.

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% with enum and defaults already documented, so the schema carries parameter semantics. The description names the three configuration levers (hours per week, days per week, weeks per year) but adds no interpretation beyond the schema, such as how biweekly/monthly are derived from weeks_per_year — baseline 3 applies.

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 ('Convierte salarios entre hora, día, semana, quincena, mes y año') and enumerates the six supported periods plus the configurable bases. It also names a near-miss sibling (interest-rate-convert), so an agent can separate pay conversion from rate conversion 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?

Explicit 'Cuándo' clause scopes use to exact/reproducible money and financial-math results (rounding, cents, rates), and an explicit 'No para' clause redirects interest-rate conversion to interest-rate-convert. Both the positive and negative conditions are stated.

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?