Loading ToolBench
AI scheduling assistant. Timezone intelligence, public holidays, business hours checking, meeting slot finder, and Google Calendar event creation. x402 native — no signup required. Pay $0.01 per call.
Server defines 6 tools with explicit schemas and descriptions. Naming follows verb_noun convention (convert_time, get_holidays, check_business_hours, find_meeting_slots, create_calendar_link, create_event). Descriptions are present but brief (avg 65 chars, below 194-char baseline). Schemas are well-formed with type declarations and parameter descriptions. Critical gaps: no output schema documentation, no error handling guidance, no parameter validation rules (e.g., timezone format, date ranges), and missing idempotency/destructiveness hints. create_event exposes access_token as a parameter (security violation). Tool composition is sound but lacks pagination for find_meeting_slots results.
Check if it is currently business hours in a timezone.
Convert a time from one timezone to another.
Generate Google Calendar and Outlook add-to-calendar links.
Create a real Google Calendar event.
Find optimal meeting times across multiple timezones.
Get public holidays for any country and year.
create_event exposes Google OAuth2 access_token as a required parameter. Credentials must never appear in tool parameters, use server-side secret injection via environment variables or vault. Agent traces log all parameters, leaking secrets into logs and prompt history.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing response structure. E.g., find_meeting_slots should document returned slot objects with start/end/timezone fields.
No error handling guidance. Errors return raw messages without recovery hints. E.g., 'Invalid time format' should suggest 'Use ISO 8601 format: 2026-06-01T14:00:00'. No categorization of retryable vs fatal errors.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Parameter constraints not documented in descriptions. E.g., 'timezone' should state 'IANA timezone identifier (e.g., Europe/London, America/New_York)' with validation rules. 'duration_minutes' lacks min/max bounds. LLMs cannot infer valid ranges.
find_meeting_slots lacks pagination. No limit parameter, no offset/cursor, no total count in response. Returning all slots for 5 days across multiple timezones could exceed context window. Should cap results at 20-50 and offer pagination.