Skip to main content
Glama

Fiches IP groupées

lookup_ips
Read-onlyIdempotent

Bulk-fetch IP intelligence records for 1–50 IPv4 or IPv6 addresses in a single call, removing duplicates and rejecting the request if any address is invalid.

Instructions

Retourne les fiches de 1 à 50 adresses en un seul appel API. Les doublons sont retirés. Une adresse invalide annule toute la requête.

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": {
      "ips": "<ips>"
    },
    "name": "lookup_ips"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipsYesAdresses IPv4 ou IPv6, 50 au maximum après dédoublonnage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: duplicates are silently removed, and a single invalid address aborts the entire request — an all-or-nothing failure mode an agent must know before batching.

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?

Three short sentences, each carrying distinct information, with the batch scope front-loaded before the dedup and failure-mode details. No filler or restatement of the title.

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?

For a single-parameter read tool with full schema coverage and clear annotations, the definition covers scope, limits, dedup and failure behavior. The only mild gap is that 'fiches' (what a returned record contains) is left vague and there is no output schema to compensate.

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

Parameters4/5

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

Schema coverage is 100% and already documents IPv4/IPv6 and the 50-item cap after deduplication, so the baseline would be 3. The description adds the error semantics of the parameter (one bad address cancels the whole call), which the schema does not convey.

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?

States a specific verb and resource ('Retourne les fiches') plus the batch scope ('de 1 à 50 adresses en un seul appel API'), which implicitly distinguishes it from the singular sibling lookup_ip. It does not name that sibling explicitly, so differentiation is inferred rather than stated.

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?

The range of 1 to 50 addresses implies the batch use case, but the description never says when to prefer lookup_ip or check_ip instead, nor any exclusion criteria. Usage is suggested by scope rather than spelled out.

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