Skip to main content
Glama

Find a date midpoint

bpj_calendar_date_midpoint
Read-onlyIdempotent

Calculate the temporal midpoint between two UTC midnights, preserving half days.

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

Input Schema

NameRequiredDescriptionDefault
endYes
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 covered. The description adds one genuinely useful behavior — inputs are interpreted as UTC midnights and results may contain half days — but 'preserving half days' is tersely phrased and the return representation is never stated, despite there being no output schema.

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 front-loaded sentence with zero filler; the operation and its key nuance are stated immediately.

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 two-parameter pure calculation this is close to adequate, but with no output schema the description should at minimum say what the result looks like — a date, a timestamp, or a fractional day count — and the half-day phrase is too ambiguous to fill that gap.

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 must carry the burden, and it only partly does: 'two UTC midnights' implies how both date strings are interpreted, but the required format (the 10-character, presumably YYYY-MM-DD input) and the inclusive nature of 'end' are left to the schema titles. Behavior when the dates are out of order or identical is not addressed.

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 uses a specific verb and resource ('Calculate the temporal midpoint between two UTC midnights') and names a distinguishing edge case ('preserving half days'), so it is clearly not a series, bounds, or ordinal-date tool. It stops short of naming any sibling as a contrast point, but the operation itself is unambiguous.

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 guidance is given: nothing says when midpoint calculation is appropriate versus bpj_calendar_date_series or bpj_calendar_month_slices, and no prerequisites or ordering constraints are stated. The agent must infer usage entirely from the tool name.

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.