Skip to main content
Glama

Calendar date validity

bpj_dq_calendar_dates
Read-onlyIdempotent

Validate YYYY-MM-DD values against calendar rollovers and leap 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": {
      "rows": "<rows>",
      "column": "<column>"
    },
    "name": "bpj_dq_calendar_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 a closed-world scope, so the safety profile is covered. The description usefully adds that the check targets rollovers (e.g. 2023-02-30) and leap days, which is real behavioral context beyond the annotations. It still does not say whether invalid rows are reported, counted, or cause an error.

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 tight sentence with the key constraint front-loaded and no wasted words. It is arguably over-terse for the gaps it leaves, but the sentence itself earns its place.

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 should indicate what a validation result looks like (per-row flags, a count, a pass/fail), and it is silent on that and on the input format for 'rows'. For a two-parameter validation tool with 0% schema coverage this leaves meaningful holes, though the core check semantics are stated.

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% — the only hints are titles 'Record array (JSON)' and 'Column name'. The description never mentions either parameter, so it does not explain that 'rows' is a serialized JSON array (max 12000 chars) or that 'column' selects which field holds the date string. With a low-coverage two-parameter schema, the description should have compensated and does not.

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 gives a specific verb ('Validate') and resource ('YYYY-MM-DD values') plus the exact failure classes it detects (calendar rollovers, leap days), which is far more informative than the title 'Calendar date validity'. It does not name or differentiate itself from adjacent siblings such as bpj_ambiguous_numeric_dates or bpj_dq_allowed_values, so it stops short of a 5.

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 or when-not-to-use guidance and no mention of alternatives in the dq_* or calendar_* families. An agent must infer from the name alone that this is a data-quality check rather than a date conversion, and nothing states prerequisites such as the input already being in ISO form.

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.