Skip to main content
Glama

Date and number format review

review_date_number_formats
Read-only

Reviews text for formats that do not travel across locales. Pass text and optionally locales (BCP 47 tags, comma-separated) and currency (ISO 4217 code, default USD). Flags numeric dates that could be day-first or month-first, English month-first dates, ordinals like 4th, mixed 12 and 24 hour clocks, comma versus period grouping used together, symbol before and after amounts, bare $ signs, percent spacing, imperial units, hard-coded plurals such as item(s) and 'x days ago', and US phone formats. Then prints a table of a fixed date, number and currency amount in each locale using the runtime's Intl data, so you can see what the same value looks like. English text patterns only; Intl output can vary a little by platform version.

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": "review_date_number_formats"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesUI copy to scan.
localesNoComma-separated BCP 47 tags. Default is 13 common locales.
currencyNoISO 4217 currency code for the amount sample. Default USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only say this is a safe read, but the description adds a great deal beyond that: it lists the specific defect classes it flags, says it secondarily prints a comparison table from the runtime's Intl data, and gives two explicit limitations ('English text patterns only', Intl output can vary by platform version). It therefore sets accurate expectations for both the checks and the sample output.

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?

The purpose comes first, then the parameters, then the list of what is flagged, then the output behavior and caveats: a sensible order with almost no filler. The long middle sentence runs together many categories, but each item is informative.

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?

Because there is no output schema, the description usefully describes the return behavior (a fixed date, number and currency sample per locale) and flags the English-only and the platform-variance limits. What is missing is how the flagged findings are reported (per-line locations? severity?), which an agent would need in order to pass the results on.

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 coverage is 100%, so all three parameters are already documented, and the description largely restates them (BCP 47 tags, comma-separated, ISO 4217, defaults). The only added meaning is the sample-table context for `currency`; this is fine, but not much more than the schema already gives.

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?

A concrete verb and resource ('Reviews text for formats that do not travel across locales') plus a full enumeration of what it looks for, so an agent knows exactly what it will get back. It does not, however, differentiate itself from close siblings like number_format_check or localisation_readiness, which an agent could easily confuse with this tool.

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?

Use is implied by 'reviews text for formats that do not travel across locales' and by the parameter explanation (pass `text`, optionally `locales` and `currency`), but there is no explicit statement of when to prefer this tool over number_format_check or review_locale_picker, and no exclusion criteria are given.

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