Skip to main content
Glama

Resolve an ISO week to Monday

bpj_calendar_iso_week_to_monday
Read-onlyIdempotent

Validate an ISO week number for its week-year and return its Monday.

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": {
      "year": "<year>",
      "week": "<week>"
    },
    "name": "bpj_calendar_iso_week_to_monday"
  }
}

Input Schema

NameRequiredDescriptionDefault
weekYes
yearYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 fully covered. The description adds one real behavioral fact — that the week is validated against the week-year, implying failure for an out-of-range week such as week 53 in a 52-week year — but never says what that failure looks like or what date format comes back.

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 tightly written sentence with the action front-loaded and zero filler. Nothing is redundant or buried.

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

Completeness3/5

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

With no output schema, the description should specify the return shape; 'its Monday' leaves the format (ISO date string vs. structured object) unstated. For a small two-parameter resolver that is a modest but real gap, alongside unstated invalid-week behavior.

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 the parameter meaning; it does add the important 'week-year' framing, warning that the year is the ISO week-year rather than the Gregorian year containing the Monday. It still does not clarify edge cases (week 1 starting in the prior December) or the accepted year range already encoded in the schema.

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?

States a specific verb pair ('validate ... and return') and a specific resource ('ISO week number', 'its Monday'), so an agent knows it maps a week-year/week pair to a concrete date. It does not differentiate itself from the closest sibling (bpj_iso_week_coordinates), leaving the agent to infer which one to pick.

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?

No when-to-use or when-not-to-use guidance; there is no mention of alternatives such as bpj_iso_week_coordinates or the other calendar tools. The context of use (converting an ISO week reference into a real calendar date) is only implied by the verb 'return'.

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.