Skip to main content
Glama

Abuseipdb

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

TDQS

A4.8/5.0
Behavior5/5

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

Discloses return of a claim_token for anonymous filings, rate-limiting ('Rate-limited to 5 per identifier per day'), no quota impact ('doesn't count against your tool-call quota'), and that feedback is read daily by the team. Annotations are all false, so the description carries the full burden and does so richly.

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?

Though longer than typical descriptions, it is dense and front-loaded with purpose and usage, then covers constraints. No filler; all sentences contribute operational information, but a slight trim would still preserve everything.

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?

Given the tool's complexity (five feedback types, context object, claim-token flow, rate limits, exclusions), the description covers everything needed for correct invocation. The absence of an output schema is mitigated by explaining the claim_token return.

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 coverage is 100%, with each parameter described. The description adds extra guidance: for claim_token, 'pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})' and notes 'with no other arguments'; for message, it says to describe issues in terms of Pipeworx tools/packs and not paste the end-user's prompt.

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 clearly states the tool's function: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It uses a specific verb+resource structure and differentiates from sibling tools like ask_pipeworx by focusing on feedback rather than questions.

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?

Provides explicit when-to-use scenarios: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise).' It also states an exclusion: 'ONLY for tools served by this Pipeworx connection' and directs other MCP tools to their respective servers.

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