Skip to main content
Glama

UTC day of an offset midnight

bpj_calendar_rfc3339_local_date
Read-onlyIdempotent

Convert local midnight at a given minute offset to UTC and report the UTC day shift.

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

Input Schema

NameRequiredDescriptionDefault
dateYes
offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and purity are covered without the description. The description adds that the operation is midnight-anchored and that the interesting output is a day shift, but it does not state the possible shift values, the treatment of DST, or the return representation — useful context, but only modestly beyond the annotations.

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 or redundancy; every clause contributes. It is terse to the point of under-specification, but nothing in it is wasted.

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 is the only place the return value could be explained, and 'report the UTC day shift' is too thin — an agent cannot tell whether it receives a UTC date, an RFC3339 string, or a -1/0/+1 delta. For a read-only conversion tool with two simple parameters this is adequate but not complete.

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 burden, and it does partially: 'local midnight' clarifies that `date` is a local calendar date and `offset` is a minute offset applied to midnight rather than an arbitrary time. However, it gives no date format string (YYYY-MM-DD) and does not explain the ±840 minute bounds or sign convention for east/west offsets, leaving real gaps.

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 names a concrete operation: take local midnight at a minute offset, convert it to UTC, and report the resulting UTC day shift. That is a specific verb+resource statement an agent can act on, though it never clarifies the output form (RFC3339 timestamp vs. a bare date vs. a numeric shift), which the tool name hints at but the description leaves open.

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 mention of the fixed-offset assumption (i.e., that this ignores DST rules), and no pointer to siblings such as bpj_convert_fixed_offset_time or bpj_dq_utc_timestamps that an agent might otherwise pick. The agent must infer the use case entirely from the name and one sentence.

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.