Skip to main content
Glama

Contrôle de risque IP

check_ip
Read-onlyIdempotent

Evaluates an IPv4 or IPv6 address and returns an allow, challenge, or block verdict with VPN, Tor, threat-level, and connection-type signals.

Instructions

Dit si une adresse IPv4 ou IPv6 paraît risquée. Retourne un verdict allow, challenge ou block, plus VPN, Tor, niveau de menace et type de connexion. block seulement pour Tor et menace high. Un type Corporate est un indice, pas un verdict.

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": "check_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesAdresse IPv4 ou IPv6 à contrôler.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds the decision rule that only Tor plus high threat yields 'block' and that Corporate type is advisory. That is meaningful context beyond the annotations, but latency, caching, behavior on unknown or malformed IPs, and any confidence signal go unmentioned.

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?

Four short sentences, front-loaded with the purpose and immediately followed by the return values and the decision rule. The Corporate caveat earns its place as a guard against misreading the output; nothing is redundant.

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?

With no output schema, the description correctly carries the burden of describing returns — verdict values plus VPN, Tor, threat level, and connection type. What remains thin is edge-case behavior (unknown IP, lookup failure) and any confidence or scoring nuance, but for a single-parameter read-only check this is close to sufficient.

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?

Only one parameter exists and schema description coverage is 100%, so the schema fully documents the `ip` field. The description's mention of IPv4 or IPv6 duplicates the schema and adds no format, CIDR, or validation details.

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 uses a specific verb and resource ('Dit si une adresse IPv4 ou IPv6 paraît risquée') and enumerates the verdicts returned, so the tool's function is unambiguous. It does not name or contrast itself with the sibling lookup_ip/lookup_ips, so an agent must infer that those are plain lookups rather than risk assessments.

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 description gives interpretation guidance — 'block seulement pour Tor et menace high' and 'Un type Corporate est un indice, pas un verdict' — which helps an agent act on the result. It never states when to choose this tool over the lookup siblings, nor any prerequisites, so the routing decision is left implicit.

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