Loading ToolBench
An MCP server giving AI agents accurate date, time, timezone, and interval information.
Three well-named, read-only tools with clear descriptions (194 - 250 chars, within baseline 34 - 392). All parameters have type strings and descriptions. Input schemas are complete and properly structured. Output schemas are documented in docstrings. No critical security issues (no secrets in params). Main gaps: no enums for constrained inputs (weekday, week_start, timezone accept free-form strings), no explicit error handling guidance in descriptions, and output schema structure not formally declared in JSON Schema format. Tool names follow verb_noun pattern (get_*, validate_*) and are unambiguous. Descriptions explain WHAT, WHEN, and WHAT IS RETURNED, meeting pattern:tool-description baseline.
Return the current date and time for an IANA timezone. Reads the real system clock — this is the tool an agent should call instead of guessing "now". The result carries an explicit UTC offset and broken-out calendar fields so no downstream parsing is ambiguous.
Return the date of a named weekday within the current week. Answers "what is the date this Wednesday?" deterministically. "This week" is anchored to today in ``timezone`` and bounded by ``week_start``.
Validate a weekday+date claim against the current week and correct it. The weekday name is authoritative: if ``claimed_date`` is not that weekday's date in the current week, ``is_correct`` is ``false`` and ``corrected_date`` gives the right date.
Weekday and week_start parameters accept free-form strings with no enum constraint. LLMs may hallucinate invalid values like 'Wednesda' or 'Tuesda' instead of valid weekday names. Should declare enum: ['Monday', 'Tuesday', ..., 'Sunday'] and 3-letter abbreviations.
Timezone parameter accepts any string; no validation or enum of IANA zones. Tool does validate at runtime and raises ValueError, but LLM has no upfront guidance on valid values. Should document common zones (UTC, Europe/London, America/New_York) or link to IANA database reference.
Output schemas documented in docstrings but not formally declared as JSON Schema in tool registration. LLMs cannot parse docstring descriptions of return structure; explicit outputSchema in tool definition would enable better planning.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
Error handling descriptions missing. When timezone is invalid or weekday is malformed, tool raises ValueError. Descriptions should guide LLM: 'If timezone is unknown, try a common zone like UTC or Europe/London. Call with a valid IANA name.'
claimed_date parameter in validate_weekday_date lacks format specification in description. Should state: 'ISO 8601 date string in YYYY-MM-DD format (e.g., 2024-12-25).' Current description only says 'ISO YYYY-MM-DD' without example or validation guidance.