Skip to main content
Glama

superhero

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

A5/5.0
Behavior5/5

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

Annotations provide no safety hints (all false), so the description carries full burden. It discloses rate limiting ('Rate-limited to 5 per identifier per day'), the anonymous claim_token flow, and that it's 'Free; doesn't count against your tool-call quota.' No contradictions with annotations.

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?

Though long, every sentence earns its place: purpose, use cases, exclusions, claim_token flow, rate limit, and cost. It is front-loaded with the core action and then layers operational details logically. No redundancy or fluff.

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?

As a feedback tool with no output schema, the description fully covers what the agent needs: how to file, how to later retrieve resolution, rules about scope, rate limits, and behavior. For the tool's complexity, it is complete and self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds substantial meaning: explains how claim_token is used to 'read whether it was fixed and what changed,' and instructs message content ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt'). This goes beyond the schema's per-field definitions.

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 purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It uses a specific verb with explicit resource (Pipeworx team) and differentiates from siblings like ask_pipeworx and discover_tools by positioning itself as a feedback channel.

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).' Also gives clear exclusions: 'ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server... file it with that server instead.'

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

All superhero 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

B3.3/5.0
Disambiguation1/5

The tool set is dominated by a huge number of unrelated tools for data lookup (Pipeworx, Polymarket, etc.), with only 4 superhero-specific tools. Many tools serve overlapping purposes (e.g., ask_pipeworx, deep_research, suggest_questions all handle general queries), making it very difficult for an agent to distinguish the right tool.

Naming Consistency2/5

Naming conventions are highly inconsistent: some tools use CamelCase (ask_pipeworx, discover_tools), others use snake_case (get_hero, list_all, compare_entities), and some use long descriptive phrases (polymarket_arbitrage, scan_competitor_ai_presence). This mixture makes it hard to predict tool names.

Tool Count1/5

With 34 tools, the count is far too large for a server named 'superhero'. Most tools are unrelated to superheroes, making the set seem bloated and misaligned with the server's stated purpose. A focused superhero server would need at most 10 tools.

Completeness1/5

For the superhero domain, the tool set is severely incomplete: only basic retrieval of heroes and powerstats, with no search, filtering, creation, comparison, or battle mechanisms. For the broader data access domain it is more complete, but that is not the server's name.

Resources