Skip to main content
Glama

greynoise_ip

Checks whether an IP is mass-scanning the internet or belongs to known benign services (RIOT), helping analysts triage suspicious network activity.

Instructions

GreyNoise community lookup: is this IP mass-scanning the internet (noise/RIOT)?

Keyless for the community endpoint; GREYNOISE_API_KEY is optional.

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

Input Schema

NameRequiredDescriptionDefault
ipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add genuinely useful operational context that structured fields lack — keyless community endpoint, optional GREYNOISE_API_KEY — but says nothing about the community endpoint's rate limits, what is returned when an IP is unknown, or the shape of the noise/RIOT verdict.

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 compact sentences with the core question front-loaded before the auth note. Nothing is padded, though the trailing whitespace/newline and the unexplained 'RIOT' acronym cost a little clarity.

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?

A one-parameter lookup with no output schema and no annotations needs only modest coverage, and the auth situation is covered. Still missing is any sense of the response (classification fields, unknown-IP behavior), which an agent needs to interpret results.

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 coverage is 0% and the single parameter is only described generically as 'ip' with an implied meaning of 'the IP to check'. The description adds no format, validation, or scope detail (e.g. IPv4 vs IPv6, public-only) beyond the field name itself.

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?

Names the specific source (GreyNoise community) and the exact question answered (is this IP mass-scanning the internet / noise vs RIOT), so the agent knows precisely what data class comes back. It does not contrast itself with adjacent tools like ip_intel or ip_whois, leaving the differentiation to inference.

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 'is this IP mass-scanning' framing implies when the tool is relevant, and the keyless note tells the agent it can be called without setup. However there is no explicit guidance on when to prefer this over ip_intel, ip_whois, or recon_ip, and no stated limits or failure conditions.

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