Skip to main content
Glama

Abuseipdb

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds valuable context: scoping to the agent's identifier (anonymous IP, BYO key hash, or account ID) and the dual behavior of retrieving a specific value or listing all keys. This goes beyond the annotations without contradicting them.

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?

The description is two sentences, front-loaded with the primary action, and includes practical examples and pairing with related tools. Every sentence contributes meaning with zero filler.

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

Completeness5/5

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

With one optional parameter, strong annotations, and a clear description covering usage, scoping, and return modes, the description is fully complete for this simple tool. No output schema exists, but the behavior is self-explanatory.

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 description coverage is 100%, and the single parameter 'key' already has a clear description. The tool description repeats that omitting it lists all keys but adds no additional syntax or format details. The schema carries the burden, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Retrieve a value previously saved via remember, or list all saved keys'. It also clarifies the two modes (with and without the key argument) and gives concrete use cases, distinguishing it from siblings like remember and forget.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'Use to look up context the agent stored earlier' and mentions it avoids re-derivation. It also names alternatives: 'Pair with remember to save, forget to delete,' providing clear context and exclusions.

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

All Abuseipdb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most tools are clearly distinct, but there are several overlapping clusters: ask_pipeworx and ask_pipeworx_beta are near-duplicates today, the Polymarket tools (edges, arbitrage, fill_risk, bet_research) have partially overlapping discovery purposes, and ai_visibility_check vs scan_competitor_ai_presence overlap on single vs multi-entity checks. These overlaps create real misselection risk, though the rest of the set splits cleanly.

Naming Consistency3/5

All names are snake_case and readable, but conventions vary noticeably: verb_noun for actions (check_ip, report_ip, list_subscriptions), domain-prefixed nouns for the Polymarket cluster (polymarket_edges, polymarket_arbitrage), and brand-prefixed meta tools (ask_pipeworx, pipeworx_feedback). Subfamilies are internally consistent, but the overall set mixes patterns.

Tool Count2/5

34 tools is already past the heavy threshold, but the bigger issue is the server name: Abuseipdb should have a handful of IP-abuse tools, yet only 3 of 34 actually relate to AbuseIPDB. The remaining 31 tools form an unrelated Pipeworx/Polymarket/memory suite, making the count wildly inappropriate for the apparent purpose.

Completeness2/5

For the declared AbuseIPDB domain, only check, report, and blacklist are covered; obvious gaps remain like removing/clearing a false report, bulk IP checks, or category metadata. The broader set is a grab bag of unrelated capabilities, so no single domain gets complete lifecycle coverage, and the nominal AbuseIPDB surface is thin and diluted.

Resources