Skip to main content
Glama

Ambiguous numeric dates

bpj_ambiguous_numeric_dates
Read-onlyIdempotent

Find slash dates where both leading fields could be month or day and report both readings.

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": {
      "text": "<text>"
    },
    "name": "bpj_ambiguous_numeric_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds that both readings are reported, which is useful behavioral context, but it says nothing about how ambiguity is decided, edge cases like day values above 12, or the shape of the results.

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?

One sentence, front-loaded with the verb and the qualifying condition, with no redundant or filler wording. Every clause carries information.

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 single-input, read-only analysis tool with no output schema, the description should convey what comes back; 'report both readings' gestures at it but leaves the actual return structure and formatting unspecified. It is adequate to select the tool but thin for predicting its results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter, 'text', whose schema title 'Source text' and maxLength make its meaning self-evident. The description adds no parameter detail, but with one obvious input argument there is little the description could contribute beyond what the schema already conveys.

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 ('Find') and a precise resource class ('slash dates where both leading fields could be month or day'), which is far more informative than the bare title. It does not explicitly contrast itself with adjacent siblings such as bpj_dq_calendar_dates, so an agent must infer the boundary from the ambiguity condition alone.

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

Usage Guidelines3/5

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

The narrow qualifying condition ('both leading fields could be month or day') implicitly tells the agent when this tool applies, but there is no explicit when-not guidance, no mention of the unambiguous-date alternative, and no statement about what input text should look like.

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.