Skip to main content
Glama

Get Time By Ip

get_time_by_ip
Read-onlyIdempotent

Get the current date and time for the timezone of an IP address (resolved via ip-api.com -> timeapi.io).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ip": "8.8.8.8"
    },
    "name": "get_time_by_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIPv4 or IPv6 address to look up

Output Schema

NameRequiredDescriptionDefault
datetimeYesISO 8601 datetime in the IP's timezone
timezoneYesIANA timezone name for the IP geolocation
utc_offsetYesUTC offset in ±HH:MM format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuine context by disclosing the external dependency chain (ip-api.com then timeapi.io), which hints at network latency and third-party failure modes, but it says nothing about fallback behavior, error cases, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and the key differentiator (timezone derived from an IP). Nothing is redundant, and the parenthetical dependency note is compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and annotations cover the safety profile. The only real gap is undefined behavior when the IP cannot be geolocated or resolved to a timezone, which an agent would want to know before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single parameter is documented as 'IPv4 or IPv6 address to look up', with examples covering both formats. The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Get') and a precisely scoped resource ('current date and time for the timezone of an IP address'), which implicitly separates it from get_time_by_timezone. It does not name that sibling or otherwise explicitly contrast the two, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Use is implied by the purpose: call it when you have an IP and want local time. There is no explicit when-to-use statement, no guidance on when to prefer get_time_by_timezone or convert_time instead, and no note about what happens for IPs without a resolvable timezone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.