Skip to main content
Glama

Generate a day-stride date series

bpj_calendar_date_series
Read-onlyIdempotent

Generate a bounded series of dates separated by a fixed day stride.

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>",
      "stride": "<stride>",
      "count": "<count>"
    },
    "name": "bpj_calendar_date_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
countYes
strideYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds only the vague word 'bounded' and repeats the stride concept; it does not say whether the input date is the first element of the output, whether output is an ordered list of date strings, or how the count interacts with the stride, which is the behavior an agent actually needs here.

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 or redundant restatement of the schema. Nothing needs to be trimmed; the problem is missing content, not excess wording.

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?

For a 3-parameter tool with no output schema and zero schema description coverage, the description is too thin. An agent cannot determine from it the date string format, inclusive/exclusive start semantics, or the shape of the returned series, all of which must be inferred.

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% – only bare titles ('Gregorian date', 'Occurrence count', 'Day stride') and min/max bounds exist. The description mentions stride and boundedness but never clarifies that 'date' is the start date, what string format it expects (maxLength 10 weakly implies ISO), or whether 'count' includes the start date. It therefore does not compensate for the coverage gap.

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 and resource ('Generate a bounded series of dates') plus the defining mechanic ('separated by a fixed day stride'), which is enough to tell it apart from single-date helpers like bpj_calendar_ordinal_date or bpj_calendar_nth_weekday. It never names a sibling or an alternative, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The agent gets no signal on when a day-stride series is preferable to siblings such as bpj_calendar_recurring_weekday_mask or bpj_business_day_offset, and no prerequisites or context are stated beyond the one-sentence purpose.

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.