Skip to main content
Glama

Fiscal quarter bounds

bpj_calendar_quarter_bounds
Read-onlyIdempotent

Determine quarter start and end using a configurable fiscal start month.

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": {
      "date": "<date>",
      "firstMonth": "<firstMonth>"
    },
    "name": "bpj_calendar_quarter_bounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
firstMonthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is fully covered. The description adds that the result is a start/end pair derived from a fiscal start month, which is useful, but it does not address edge cases such as whether the end date is inclusive or how a start month of 1 behaves.

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?

A single, front-loaded sentence with no wasted words. It is efficient, though the terseness leaves the input format and return semantics unexplained.

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?

For a simple two-parameter read-only tool with full annotation coverage and no output schema, the description conveys the core computation and the meaning of the fiscal-month input. It remains incomplete on date format, the inclusive/exclusive nature of the end bound, and the exact return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It explains 'firstMonth' as a fiscal start month (matching the schema title), but adds nothing about the 'date' parameter's expected format (maxLength 10 suggests ISO YYYY-MM-DD but this is left implicit) or how the fiscal month shifts the quarter boundaries.

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 states a specific verb ('Determine') and a specific resource ('quarter start and end'), plus the key configurator ('configurable fiscal start month'). It is clearly distinguishable from siblings like month_end_offset or iso_week_to_monday, though it does not name any sibling explicitly.

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 phrase 'configurable fiscal start month' implies the intended context (fiscal years that do not begin in January), but there is no explicit when-to-use or when-not-to-use guidance. No alternative tool is named for calendar-year quarter boundaries.

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.