Burs-IA Utils

Año y trimestre fiscal

fiscal-period

Read-onlyIdempotent

Calcula, para una fecha y el mes de inicio del año fiscal, el año, trimestre y mes fiscal con sus límites. Cuándo: un resultado de fechas, zonas horarias o calendario tiene que ser exacto (desfases, horario de verano, fines de mes, bisiestos). No para: describir un año y mes (month-info). 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: Computes, for a date and the month the fiscal year starts, the fiscal year (named by its ending calendar year or its starting year), fiscal quarter, fiscal month and period bounds. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: describing a year and month (month-info). 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	Default
`date`	Yes	Date YYYY-MM-DD (string; required; up to 10 chars; format date).
`naming`	No	Name FY by (optional; one of: end_year, start_year; default "end_year").	end_year
`start_month`	No	Fiscal year start month 1-12 (integer; optional; default 1; min 1; max 12).

Output Schema

Name	Required	Description	Default
`year_end`	No
`year_start`	No
`fiscal_year`	No
`quarter_end`	No
`fiscal_month`	No
`quarter_start`	No
`fiscal_quarter`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-10-31"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Computes, for a date and the month the fiscal year starts, the fiscal year (named by its ending calendar year or its starting year), fiscal quarter, fiscal month and period bounds. When: a date, time-zone or calendar result has to be exact (offsets, daylight saving, month ends, leap years). Not for: describing a year and month (month-info). 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.6/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 safety is covered. The description adds genuinely new operational context – no stored state, explicit limits (64 KB input, 1 s per call, 1 MB output) – though 'deterministic' largely restates idempotentHint.

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?

The EN body is front-loaded and well-structured with When/Not-for/Side effects/Limits. However the full ES and EN versions are duplicated in the same field, and the trailing '[EN completo / full EN: inputSchema.description]' placeholder is noise that costs tokens without adding meaning.

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 not be spelled out; the description nonetheless enumerates the key outputs (fiscal year, quarter, month, bounds), and annotations cover the safety profile. Nothing needed to invoke it 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?

Schema coverage is 100%, so baseline is 3. The description earns a bump by explaining what 'naming' means semantically (fiscal year labeled by its ending calendar year vs its starting year), which the enum description alone does not convey.

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 (computes/calcula) plus the concrete outputs (fiscal year, quarter, fiscal month, period bounds) and the inputs that drive them (date + start month). It also names the naming convention choice, so an agent can distinguish this from date/calendar siblings.

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 'When:' clause (exact date/timezone/calendar results with offsets, DST, month ends, leap years) and 'Not for:' clause that names the competing sibling month-info. The positive and negative conditions are both present, leaving nothing to inference.

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?