Skip to main content
Glama

Expand a weekly weekday mask

bpj_calendar_recurring_weekday_mask
Read-onlyIdempotent

Expand chosen ISO weekdays into matching dates in an inclusive range of up to one year.

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>",
      "weekdays": "<weekdays>"
    },
    "name": "bpj_calendar_recurring_weekday_mask"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
dateYes
weekdaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one real behavioral fact not in the schema: the range is inclusive and capped at one year. It does not say what happens if the range exceeds a year, whether results are sorted, or how the dates are formatted.

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?

One sentence, front-loaded with the core transformation, with the range constraint attached where it is immediately useful. No filler, no repetition of the tool name.

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?

With only three flat string parameters, no output schema, and full annotation coverage, the definition is nearly sufficient: it states input semantics, the one-year bound, and that the output is matching dates. The remaining gaps (output ordering and date string format) are minor for a deterministic read-only expansion.

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 carries real weight, and it does clarify two things: the range endpoint is inclusive, and the weekday values are ISO weekdays. It still never says whether weekdays are numbers (1-7) or names, or what date format is expected, which are the exact ambiguities a 0%-coverage schema leaves open.

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?

"Expand chosen ISO weekdays into matching dates" gives a specific verb (expand) and a specific transformation (weekday mask -> concrete dates), which separates it from neighbors like bpj_calendar_date_series or bpj_calendar_nth_weekday. It stops short of naming any sibling or contrasting behavior, so the differentiation is inferred from the wording alone.

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 "inclusive range of up to one year" implies the operating context and a hard limit, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative for ranges longer than a year. The agent must infer the use case from the verb.

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.