Loading ToolBench
Single tool with minimal definition quality. Tool name 'get_current_date_time' follows verb_noun convention (+), but description is only 56 characters and lacks context on when/why to use it. Input schema is completely empty ({}), violating the critical requirement that every parameter needs a description and type. No output schema documented. No error handling guidance. No parameter descriptions (there are none to describe, but the empty schema itself is a red flag for a tool that could benefit from optional parameters like timezone or format). This server barely meets the threshold for a functional tool definition.
Get the current local date and time in ISO 8601 format
Empty input schema ({}). No parameters documented, no types, no descriptions. Violates pattern:tool requirement that every parameter must have a description and type definition.
No output schema documented. LLMs cannot plan downstream operations or extract fields from the response. Violates pattern:tool requirement for documented return types.
Description is only 56 characters and lacks context. Does not explain WHEN to use this tool, WHAT it returns, or any prerequisites. Baseline for A+ tools is 194 chars average; this is 29% of that.
No error handling guidance. Tool returns a String but does not document what happens on failure (e.g., system clock unavailable, timezone resolution failure). No recovery hints for LLMs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
No optional parameters for timezone, format, or locale. Tool is inflexible, agents cannot request time in a specific timezone or format, forcing workarounds or post-processing.