Get the current local time for an IP address via geolocation, or omit the IP to use your own. Use it to determine time zones and local time for remote users or systems.
Get current time based on IP address geolocation.
| Name | Required | Description | Default |
|---|---|---|---|
| ip | No | IP address (omit for your own IP) |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds that the result is derived from IP geolocation, which hints at imprecision for VPN/proxy users, but it does not state that caveat or what happens when geolocation fails.
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?
One front-loaded sentence with no wasted words. It is appropriately sized, though it is almost too terse to carry any usage or behavioral signal.
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?
For a single-optional-parameter read tool with full schema coverage and clear annotations, the description is nearly sufficient. The gaps are minor: no mention of accuracy limits or fallback behavior when IP cannot be resolved.
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% and already documents that omitting ip uses your own IP. The description adds no syntax, format, or default behavior beyond the schema, so baseline 3 applies.
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?
Clear verb+resource (get current time) plus the distinguishing mechanism (IP geolocation), which separates it from worldtime_by_timezone. However, it never names that sibling or states the contrast explicitly, so an agent must infer the difference.
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?
Usage is only implied: geolocation-based time is useful when the caller's location is unknown or the IP is the source of truth. There is no explicit when-to-use/when-not or pointer to worldtime_by_timezone / datetime_current_time.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.