Skip to main content
Glama

superhero

by io.github.pipeworx-io

Get Hero

get_hero
Read-onlyIdempotent

Get full data for a superhero by their numeric ID, including powerstats, biography, appearance, and images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric superhero ID (1–731)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric superhero ID
nameYesSuperhero name
slugYesURL-friendly slug identifier
workYesWork and occupation details
imagesYesCharacter images in multiple sizes
biographyYesBiography information
appearanceYesPhysical appearance details
powerstatsYesPower statistics
connectionsYesConnections and relationships

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds value by specifying the return content, which is useful context. No additional behavioral traits are disclosed, but with annotations covering safety, this is sufficient.

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, front-loaded with the verb and resource, and zero wasted words. It clearly communicates purpose and scope.

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?

For a simple single-parameter tool with a rich output schema and strong annotations, the description is complete enough. It states what is returned and the key input requirement, and the output schema covers return details.

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 100% and the parameter description already provides the ID range (1–731). The description only repeats 'numeric ID' without adding new semantics, 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?

Description clearly states the tool returns full superhero data by numeric ID, listing content categories (powerstats, biography, appearance, images). This distinguishes it from siblings like get_biography and get_powerstats.

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

Usage Guidelines4/5

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

The description implies use when complete hero data is needed, but does not explicitly mention alternatives or exclusions. Sibling tools exist, so the context is clear enough for an agent to infer when to use this over more specific tools.

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