Skip to main content
Glama

WritersLogic verifiable AI agents

fiscal-period

Fiscal year, quarter and period for a date: month-aligned or 52/53-week (4-4-5, 4-5-4, 5-4-4) calendars — Maps up to 100 dates to a fiscal year, quarter, period and week for a caller-defined fiscal calendar: a month-aligned year (starts on day 1 of a named month) or a 52/53-week year ending on a given weekday last in or closest to a month end, in a 4-4-5, 4-5-4 or 5-4-4 pattern with the 53rd week appended to the final period; detects 53-week years and checks an asserted fiscal year, quarter or period.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "yearLabel": "<yearLabel>",
      "items": "<items>"
    },
    "name": "fiscal-period"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
itemsYes
endRuleNo52-53-week: last endWeekday in endMonth, or the endWeekday closest to endMonth's last day.
patternNo52-53-week: weeks per period within each quarter.
endMonthNo52-53-week: month near whose end the year ends.
yearLabelYesstart: the fiscal year is named for the calendar year it begins in. end: for the calendar year it ends in (US federal FY2027 begins 2026-10-01).
endWeekdayNo52-53-week: weekday the year ends on, 0=Sunday.
startMonthNomonth-aligned: month in which the fiscal year starts, on day 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well: it discloses the 100-date batch cap, how 53-week years arise and where the 53rd week is appended, and that asserted year/quarter/period values are checked. The remaining gap is that it never says whether a failed assertion produces an error or a flagged result, and it does not describe the response shape.

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?

It is a single dense sentence-complex, but the purpose is front-loaded and every clause carries information about the calendar models or the validation behavior. No filler or marketing language. The density makes it harder to scan than an ideally structured definition, keeping it just below 5.

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

Completeness3/5

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

With 8 parameters, 3 required, conditional by calendar type, no output schema and no annotations, the description should at minimum sketch what each item's result looks like and what happens when claimedPeriod/claimedQuarter/claimedFiscalYear disagree with the computed value. Those two gaps are material for correct invocation, though the core computation is well covered.

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 75% and the enum fields already carry their own descriptive text for endRule, pattern, yearLabel, endWeekday, endMonth and startMonth. The description reinforces the semantics (day-1-of-startMonth for month-aligned, last-vs-closest endWeekday, week patterns with the 53rd week appended) but adds little that is not already in the schema. It does implicitly scope which parameters belong to which calendar type, which is a small plus.

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 description opens with a concrete verb-and-resource framing (maps dates to fiscal year, quarter, period, week) and enumerates the two supported calendar families plus the validation variant. It is unmistakably a fiscal-calendar computation tool. It does not name or differentiate itself from any sibling (e.g. calendar-convert), which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

The usage context is implied by the parameterization: month-aligned versus 52/53-week with a 4-4-5/4-5-4/5-4-4 pattern, and the mention of checking asserted fiscal year/quarter/period hints at a validation use case. However, there is no explicit statement of when to choose this over an alternative calendar tool, nor any prerequisite or exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources