Skip to main content
Glama
openapi-mcp-sdk

openapi-mcp-sdk

check_ip_advanced

check_ip_advanced
Read-onlyIdempotent

Retrieves detailed IP address intelligence, including geolocation, ISP, connection type, abuse history, VPN/Tor status, bot signals, and fraud score to assess risk and origin.

Instructions

Retrieves advanced information about an ip address (ip, createdAt, updatedAt, state, requestedIp, message, success, proxy, host, isp, organization, asn, countryCode, city, region, timezone, latitude, longitude, zipCode, isCrawler, connectionType, recentAbuse, abuseVelocity, botStatus, frequentAbuser, highRiskAttacks, sharedConnection, dynamicConnection, securityScanner, trustedNetwork, operatingSystem, browser, deviceBrand, deviceModel, transactionDetails, errors, vpn, tor, activeVpn, activeTor, mobile, fraudScore) Args: ip: valid ip number

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_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered structurally. The description's contribution is the return-field inventory, which is genuinely useful given there is no output schema, but it says nothing about failure modes, error payloads, or what happens with an unresolvable or malformed address.

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?

Two sentences, front-loaded with the verb and resource. The long comma-separated field list is bulky and unstructured, but it earns some of its place because no output schema exists to convey the return shape.

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

Completeness3/5

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

For a one-parameter read-only lookup the definition covers the essentials, and the field inventory compensates for the missing output schema. It still leaves gaps an agent needs: accepted IP formats, behavior on invalid input, and how it relates to the async siblings.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must carry the burden. "valid ip number" is the bare minimum and is slightly misleading since the schema types it as a string; it does not say whether IPv4, IPv6, or CIDR is accepted or give any format example.

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 ("Retrieves advanced information about an ip address") and the parenthetical inventory makes the kind of data returned concrete. It does not explicitly contrast itself with sibling lookups like check_email_advanced or check_url_advanced, but the resource noun is distinctive enough to distinguish it.

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 guidance on when to call this versus the sibling checks, no note that it is a synchronous counterpart to *_start / check_async_status flows, and no prerequisites such as credentials or rate limits. The only usage text is the terse "Args: ip: valid ip number".

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