Skip to main content
Glama

ip_reputation

Read-only

Screen one IP for reputation risks for 0.001 USDC, or check a batch of up to 100 IPs for 0.050 USDC.

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": {
      "mode": "<mode>",
      "input": "<input>"
    },
    "name": "ip_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes
inputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely useful behavior beyond that — per-call pricing for both modes — but omits payment mechanics, failure behavior, and what a partial batch failure costs.

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?

A single sentence that front-loads the action and puts the two modes and their costs in parallel structure. Zero filler; every clause carries information the agent needs to pick a mode.

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 two-parameter tool with no output schema, the description covers the essential decision points (mode, volume limit, cost) and annotations cover the safety profile. It stops short of describing the reputation result shape or the per-IP failure behavior, which would help an agent on a batch call.

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 description coverage is 0%, so the description carries real burden: it explains that 'single' takes one IP and 'batch' takes up to 100, and it prices each mode, which meaningfully maps to the 'mode' enum. It still does not explain the mode-to-input-shape binding, accepted IP formats, or why the schema's nested note says 'Stapel bis 25 Adressen' while the description claims 100.

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 ("Screen one IP for reputation risks") and distinguishes the two operating scopes (single IP vs batch of up to 100) with their respective prices. An agent can tell what it does and its two modes without opening the schema, though it does not differentiate itself from the sibling tools (domain_profile, email_batch).

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 single-vs-batch framing implicitly tells the agent to choose a mode based on input volume, and the price difference gives a cost-based selection signal. However, it never says when to prefer this tool over a sibling such as domain_profile, nor what prerequisites (payment/credits) must be in place before calling.

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