Skip to main content
Glama

Split an interval by month

bpj_calendar_month_slices
Read-onlyIdempotent

Split an inclusive date interval into calendar-month slices over at most 120 months.

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>",
      "end": "<end>"
    },
    "name": "bpj_calendar_month_slices"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
dateYes

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?

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds a real behavioral constraint (the 120-month cap) but does not say whether exceeding it errors or truncates, nor how partial first/last months are handled.

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 front-loaded sentence with no filler; the operation, the input shape, and the hard limit all appear before any trailing detail.

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

Completeness2/5

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

With no output schema and no parameter descriptions, the return value is entirely undisclosed: an agent cannot tell whether it gets a list of date pairs, strings, or counts. For a splitting tool whose whole value is its output structure, this is a significant omission.

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 must carry the load, and it only supplies the notion of an inclusive interval. It never states the expected date format, never clarifies that 'date' is the interval start (its schema title is just 'Gregorian date'), and says nothing about slice boundary semantics.

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?

Names a specific verb (split) and resource (calendar-month slices) plus the scope (an inclusive date interval), which is precise enough to distinguish it from offset/layout siblings like bpj_calendar_month_end_offset and bpj_calendar_month_layout. It stops short of explicitly saying how it differs from a general series tool such as bpj_calendar_date_series.

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: an agent can infer it is for decomposing an interval into per-month buckets, and the 'at most 120 months' clause signals a bounded-input expectation. There is no explicit when-to-use, when-not-to-use, or named alternative.

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.