Skip to main content
Glama

Gregorian Julian day number

bpj_calendar_julian_day_number
Read-onlyIdempotent

Return the integer Julian day number at UTC noon on the supplied Gregorian date.

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

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 usefully adds the computational convention (integral value at UTC noon, avoiding a fractional day) and the return type (integer), but says nothing about accepted date formats, invalid-input behavior, or supported date ranges.

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 returned value, with every clause adding information (type, reference point, input domain). No filler or redundancy.

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?

For a simple pure-function converter with one parameter and no output schema, the description covers the return type and the noon convention adequately. The missing piece is the accepted input date format, which the agent must guess from maxLength alone before it can call the tool correctly.

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 carries the burden for the single date parameter, and it only restates "supplied Gregorian date" — the same wording as the schema title. It never states the expected format (e.g., YYYY-MM-DD), despite the schema's maxLength of 10 being the only hint.

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 states a specific verb and resource ("Return the integer Julian day number") plus a precise reference point ("UTC noon on the supplied Gregorian date"), which implicitly separates it from midnight-based siblings like bpj_calendar_mjd_at_midnight. It stops short of naming any alternative outright, so an agent must infer the distinction from the noon convention.

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 guidance, no exclusions, and no reference to alternatives such as the MJD or ordinal-date tools in the same family. The agent can infer the use case from the computed value, but nothing tells it when this tool is the right choice versus a neighboring calendar converter.

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.