Superhero

Get Hero

get_hero

Read-onlyIdempotent

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Numeric superhero ID (1–731)

Output Schema

Name	Required	Description
`id`	Yes	Numeric superhero ID
`name`	Yes	Superhero name
`slug`	Yes	URL-friendly slug identifier
`work`	Yes	Work and occupation details
`images`	Yes	Character images in multiple sizes
`biography`	Yes	Biography information
`appearance`	Yes	Physical appearance details
`powerstats`	Yes	Power statistics
`connections`	Yes	Connections and relationships

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "appearance": {
+      "description": "Physical appearance details",
+      "properties": {
+        "eyeColor": {
+          "description": "Eye color",
+          "type": "string"
+        },
+        "gender": {
+          "description": "Gender",
+          "type": "string"
+        },
+        "hairColor": {
+          "description": "Hair color",
+          "type": "string"
+        },
+        "height": {
+          "description": "Height in different units",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "race": {
+          "description": "Race or species",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "weight": {
+          "description": "Weight in different units",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "biography": {
+      "description": "Biography information",
+      "properties": {
+        "aliases": {
+          "description": "List of aliases",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "alignment": {
+          "description": "Moral alignment (good, bad, neutral)",
+          "type": "string"
+        },
+        "alterEgos": {
+          "description": "Alternative identities",
+          "type": "string"
+        },
+        "firstAppearance": {
+          "description": "First appearance in comics",
+          "type": "string"
+        },
+        "fullName": {
+          "description": "Full legal name",
+          "type": "string"
+        },
+        "placeOfBirth": {
+          "description": "Birthplace",
+          "type": "string"
+        },
+        "publisher": {
+          "description": "Publisher (Marvel, DC, etc.)",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "connections": {
+      "description": "Connections and relationships",
+      "properties": {
+        "groupAffiliation": {
+          "description": "Team or group affiliations",
+          "type": "string"
+        },
+        "relatives": {
+          "description": "Known relatives",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "id": {
+      "description": "Numeric superhero ID",
+      "type": "number"
+    },
+    "images": {
+      "description": "Character images in multiple sizes",
+      "properties": {
+        "lg": {
+          "description": "Large image URL",
+          "type": "string"
+        },
+        "md": {
+          "description": "Medium image URL",
+          "type": "string"
+        },
+        "sm": {
+          "description": "Small image URL",
+          "type": "string"
+        },
+        "xs": {
+          "description": "Extra small image URL",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "name": {
+      "description": "Superhero name",
+      "type": "string"
+    },
+    "powerstats": {
+      "description": "Power statistics",
+      "properties": {
+        "combat": {
+          "description": "Combat stat (0-100 or null)",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "durability": {
+          "description": "Durability stat (0-100 or null)",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "intelligence": {
+          "description": "Intelligence stat (0-100 or null)",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "power": {
+          "description": "Power stat (0-100 or null)",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "speed": {
+          "description": "Speed stat (0-100 or null)",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "strength": {
+          "description": "Strength stat (0-100 or null)",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "slug": {
+      "description": "URL-friendly slug identifier",
+      "type": "string"
+    },
+    "work": {
+      "description": "Work and occupation details",
+      "properties": {
+        "base": {
+          "description": "Base of operations",
+          "type": "string"
+        },
+        "occupation": {
+          "description": "Primary occupation",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "slug",
+    "powerstats",
+    "appearance",
+    "biography",
+    "work",
+    "connections",
+    "images"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": 1
+  },
+  {
+    "id": 100
+  }
+]

First observedApr 14, 2026

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 tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.