Returns the current date and time in UTC and, if a city is provided, in the local timezone. Call this before create_order to get the correct timezone offset.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | Optional city name to get local time and offset. Valid: Ottawa, Gatineau, Toronto, Montreal, Surrey, Miami. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It explains the output includes UTC and optional local time, but does not explicitly confirm it's read-only or describe any side effects. Adequate for a simple retrieval tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose. Every sentence provides necessary information without redundancy or waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, so description should clarify return format. It states returns UTC and local time/offset, but does not specify format (e.g., ISO string, number). Adequate for a simple tool but could be more explicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with description of valid city values. Description adds context by stating behavior when 'city' is provided (local timezone). Adds value beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns current date and time in UTC and optionally in a city's local timezone. This distinguishes it from sibling tools which focus on orders, quotes, and job management.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises calling before 'create_order' to get the correct timezone offset. No alternatives or when-not-to-use instructions are given, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: quoting, ordering, job cancellation, job rescheduling, profile retrieval, service availability lookup, scheduled jobs listing, and current datetime. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern in snake_case, such as calculate_quote, cancel_job, get_profile, etc. No mixing of conventions.
8 tools is well-scoped for a home services booking server. It covers the essential customer-facing operations without being too few or excessive.
The tool set covers the core workflow: checking services, getting quotes, creating orders, managing jobs (view, cancel, reschedule). Minor gap: no tool to update profile or payment method, but the surface is largely complete for the stated purpose.
