Skip to main content
Glama

Fiche IP

lookup_ip
Read-onlyIdempotent

Get geolocation, timezone, currency, connection and security details for any IPv4 or IPv6 address; use the fields parameter to return only the data you need.

Instructions

Retourne la fiche IP Who d’une adresse : géolocalisation, fuseau, drapeau, devise, connexion et sécurité. Le paramètre fields limite la réponse aux champs demandés, par exemple country, city, security.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ip": "<ip>"
    },
    "name": "lookup_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesAdresse IPv4 ou IPv6.
fieldsNoChamps à conserver. Sans liste, la fiche complète.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context about the categories of data returned and the fields filter, but it does not disclose rate limits, authentication requirements, error behavior, or response structure.

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

Conciseness4/5

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

The definition is two front-loaded sentences with no filler. It is efficient, though the explanation of the fields parameter overlaps slightly with what the schema already states.

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?

This is a simple two-parameter read tool with no output schema. The description lists the main categories of returned data and explains the optional field filtering, which is sufficient for an agent to call it correctly, though the exact response shape is not described.

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%, so both parameters are already documented in the input schema. The description adds example field names such as country, city and security, which is modest extra value beyond the schema, but it does not explain field syntax or validation constraints.

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 states a specific verb and resource: it returns an IP record for an address, listing geolocation, timezone, flag, currency, connection and security data. The purpose is clear, but it does not distinguish this tool from siblings such as lookup_ips or check_ip.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives. The phrase 'd’une adresse' implies a single-IP lookup, but the description never says when to choose this over a batch or check tool.

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

Deploy Server

Other Tools