Skip to main content
Glama

Resolve an ordinal day

bpj_calendar_from_ordinal
Read-onlyIdempotent

Resolve a day number within a year, respecting leap-year limits.

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>",
      "ordinal": "<ordinal>"
    },
    "name": "bpj_calendar_from_ordinal"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
ordinalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description adds the leap-year validity behavior, which is useful. It says nothing about error behavior for ordinal 366 in a common year, nor what form the resolved day takes, and no output schema exists to fill that gap.

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?

A single front-loaded sentence with no filler. It is appropriately brief for a two-parameter pure computation, though the brevity contributes to the gaps noted in other dimensions.

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?

The tool is simple and the annotations cover safety, but with no output schema the description should say what is returned (a calendar date, and in what form) rather than leave the agent to infer 'resolve' means 'produce a date'. The leap-year caveat is a genuine start, but the return contract is missing.

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% with only bare titles and min/max bounds, so the description must compensate. 'Respecting leap-year limits' adds real meaning: ordinal 366 is only valid in leap years, so the effective upper bound of the 'ordinal' parameter depends on 'year'. It still does not state the accepted year semantics (proleptic Gregorian per the title) or what happens on an out-of-range ordinal in a non-leap year.

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 and resource: 'Resolve a day number within a year' tells the agent this converts (year, ordinal) into a date. The 'leap-year limits' clause hints at the constraint. It does not, however, name or contrast the sibling bpj_calendar_ordinal_date, which appears to be the inverse direction, so sibling differentiation is left to inference.

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 implied by the phrasing: call this when you have a year and a day-of-year and want the corresponding date. There is no explicit when-to-use, when-not-to-use, or pointer to the inverse sibling for date-to-ordinal conversion, leaving the agent to reason from the name alone.

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.