Skip to main content
Glama

Resolve a modified Julian day

bpj_calendar_mjd_at_midnight
Read-onlyIdempotent

Resolve an integer Modified Julian Date at midnight UTC to a 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": {
      "mjd": "<mjd>"
    },
    "name": "bpj_calendar_mjd_at_midnight"
  }
}

Input Schema

NameRequiredDescriptionDefault
mjdYes

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 the tool as read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful behavioral context by specifying that the conversion is at midnight UTC, but it does not describe handling of invalid inputs or the exact output representation.

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?

The description is a single front-loaded sentence with no unnecessary wording. Every phrase earns its place by specifying the input type, conversion direction, time basis, and output calendar.

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?

For a simple one-parameter deterministic conversion with read-only annotations and no nested structures, the description supplies the essential context. It could be slightly more complete by stating the return format, since no output schema is provided.

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?

With one parameter and 0% schema description coverage, the description must carry meaning. It clarifies that the input is an integer Modified Julian Date and that the interpretation is midnight UTC, but it does not explain the schema’s range boundaries or deeper MJD semantics.

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 conversion (“Resolve … to a Gregorian date”) with the exact input domain (“integer Modified Julian Date at midnight UTC”). It is clear what the tool does, though it does not explicitly name or contrast itself with sibling calendar conversions such as Julian day number or ordinal date.

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?

The description only states the operation; it gives no guidance on when to use this tool versus related calendar tools, nor any exclusions or prerequisites. The use case is inferable from the purpose, but no explicit usage guidance is provided.

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.