Skip to main content
Glama

Shift by calendar months

bpj_calendar_month_end_offset
Read-onlyIdempotent

Shift a date by signed calendar months, clamping its day to the target month end.

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>",
      "months": "<months>"
    },
    "name": "bpj_calendar_month_end_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
monthsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent, closed-world read, so the description's job is to add the non-obvious semantics — and it does, by disclosing the month-end clamping (e.g. a 31st clamps in a 28/29/30-day month). It does not disclose that clamping is lossy (the original day is not recoverable on a reverse shift) or what happens with malformed dates, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the action and the key behavioral qualifier front-loaded and no filler. Every clause earns its place.

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?

For a two-parameter pure calendar function with rich annotations and no output schema, this covers the essential behavior. The remaining gaps — input date format and the lossy nature of clamping — are modest but would matter to an agent constructing calls or chaining results.

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 0%, so the description must carry parameter meaning. It clarifies that 'months' is signed (covering past and future shifts) and defines the clamping applied to 'date', but it never states the expected date string format (the schema only hints via maxLength: 10) or the accepted date range, leaving a real gap for the required 'date' parameter.

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 gives a specific verb ('Shift') and resource ('a date'), plus the qualifying unit ('signed calendar months') and the clamping rule, which separates it from day-based siblings like bpj_business_day_offset or layout tools such as bpj_calendar_month_layout. It does not name a sibling explicitly, so it stops short of a 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?

Usage is only implied by the purpose: an agent can infer this is the tool for month-granular date arithmetic. There is no explicit statement of when to prefer it over week/day shifters or boundary tools (e.g. bpj_calendar_quarter_bounds), and no prerequisites or exclusions are given.

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.