Skip to main content
Glama

BRAINIAC Telecom & Network Infrastructure Intelligence

Check IP address reputation

network-intelligence_ip-address-reputation-check

Check caller-supplied IP reputation labels/scores only. No paid reputation API is used and private networks are not scanned. Price $0.03 USDC. POST /api/v1/network-intelligence/ip-address-reputation-check. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "network-intelligence_ip-address-reputation-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
logsNo
textNo
filesNo
configsNo
bgpRoutesNo
incidentsNo
publicDnsNo
publicTlsNo
dnsRecordsNo
reputationsNo
certificatesNo
latencySamplesNo
latencyAnomalyZNo
expiryWarningDaysNo
packetLossSamplesNo
packetLossWarnPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful operational traits beyond the name: a $0.03 USDC charge, no third-party reputation API, no private-network scanning, and a 402 response for unpaid calls that do not run. It still omits what the tool actually returns and whether read-only/idempotent, so it is strong but not complete.

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 with the scope constraint front-loaded, followed by the cost/payment model and endpoint. Every sentence carries information; the only mild weakness is that pricing and HTTP plumbing are presented before any parameter or return context.

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

Completeness2/5

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

For a tool exposing 20 parameters with nested objects, no annotations, no output schema and zero schema descriptions, the description leaves the agent guessing about the other input families (logs, configs, BGP routes, TLS, latency) and the shape of results. It covers scope, pricing and payment behavior well but is not complete enough to call the tool confidently.

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% across 20 parameters, several of them large nested arrays (logs, configs, bgpRoutes, latencySamples), so the description must compensate and largely does not. Only the 'reputations' concept is loosely hinted at by 'labels/scores'; csv, asOf, file/files, json, text, publicDns, publicTls and the rest receive no explanation at all.

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 first sentence names a specific verb and resource ('Check ... IP reputation labels/scores') and adds a sharp scope qualifier: caller-supplied data only. That scope statement lets an agent distinguish this from tools that would enrich with third-party APIs. It stops short of naming any sibling explicitly, so it is clear but not sibling-differentiating.

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?

Usage is implied rather than stated: 'caller-supplied ... only' and 'no paid reputation API' tell the agent this tool consumes its own reputation records, and 'private networks are not scanned' hints at a boundary. There is no explicit when-to-use vs when-not-to-use guidance, and no alternative tool is named for the external-lookup case.

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.

Resources