Skip to main content
Glama

WritersLogic business agents

date-claim-check

Does this date fall on the claimed weekday? (batch, year boundaries and leap days) — Checks up to 200 claims 'Monday 2026-12-28' against the proleptic Gregorian calendar and reports the real weekday, whether the date exists (2026-02-29 does not), and the nearest date carrying the claimed weekday; a claim 'Friday, 13 March' without a year returns the years in a range where it holds. Built for an agent verifying dates in a document, email or itinerary. Gregorian only (no Julian 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": {
      "items": "<items>"
    },
    "name": "date-claim-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
toYearNo
fromYearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it discloses the 200-claim cap, the proleptic Gregorian calendar assumption, that impossible dates like 2026-02-29 are reported as nonexistent, and that a nearest matching date is returned. What it lacks is a statement of the default year range (the schema allows 1583-2999) and the sentence is visibly truncated at '(no Julian date', leaving the calendar limitation incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading question is well front-loaded, but the body is one dense run-on paragraph with heavy parenthetical packing and an abrupt truncated ending. Most clauses carry real information, yet the packaging makes it harder to scan than a short bulleted structure would.

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 three-parameter, no-annotation, no-output-schema tool, the description covers the inputs' effect, the calendar basis, batch limits and failure modes well. The gaps are the truncated final sentence and the unstated year-range defaults, which matter for the monthDay path but do not block correct invocation.

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?

The description conveys the semantics of the monthDay-plus-year-range mode ('a claim Friday, 13 March without a year returns the years in a range where it holds') and the batch limit, which genuinely adds meaning since schema coverage is 0% for the top-level properties. However, it never names fromYear or toYear, nor their 1583-2999 bounds and defaults, so an agent must map the concept back to the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a direct question that names the exact operation (checking a date against a claimed weekday) and immediately scopes it with batch size, year boundaries and leap days. An agent can distinguish this from sibling checker tools like time-bucket-check or dst-check without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Built for an agent verifying dates in a document, email or itinerary' gives a clear use context, and the month-day-without-year case signals when the fromYear/toYear range matters. It stops short of naming alternatives or stating when not to use it, so it stops at clear context without exclusions.

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.

Resources