Skip to main content
Glama

Weekday distribution of a date range

bpj_calendar_weekday_histogram
Read-onlyIdempotent

Count occurrences of each ISO weekday in an inclusive range.

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_weekday_histogram"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds the useful detail that the range is inclusive, but it says nothing about output shape, invalid or reversed ranges, or date format.

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?

One short, front-loaded sentence with no waste. It could have used the space for format or return-value detail, but nothing is redundant.

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?

There is no output schema, so the description should explain what the result looks like (e.g., counts keyed by ISO weekday 1–7). Combined with undocumented date format, the definition is thin for an agent trying to call and interpret the tool.

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 needs to carry parameter meaning. It only reinforces the inclusivity already stated in the 'End date (inclusive)' title and leaves date format, ordering constraints, and the Gregorian-to-ISO weekday relationship unaddressed.

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: 'Count occurrences of each ISO weekday in an inclusive range.' It clearly differs from siblings like bpj_calendar_nth_weekday or bpj_calendar_last_weekday, though it doesn't name any of them.

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 statement of when to use this versus alternatives such as bpj_calendar_recurring_weekday_mask or the other weekday tools, and no exclusions or prerequisites are given. Usage is only implied by the sentence itself.

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.