Superhero

Get Powerstats

get_powerstats

Read-onlyIdempotent

Get power statistics (intelligence, strength, speed, durability, power, combat) for a superhero by ID.

Input Schema

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

Output Schema

Name	Required	Description
`power`	Yes	Power stat (0-100 or null)
`speed`	Yes	Speed stat (0-100 or null)
`combat`	Yes	Combat stat (0-100 or null)
`strength`	Yes	Strength stat (0-100 or null)
`durability`	Yes	Durability stat (0-100 or null)
`intelligence`	Yes	Intelligence stat (0-100 or null)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+      ]
+    }
+  },
+  "required": [
+    "intelligence",
+    "strength",
+    "speed",
+    "durability",
+    "power",
+    "combat"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

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

First observedApr 14, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, and the description adds a list of included stats but no further behavioral context like error cases or return format beyond what the output schema likely covers.

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, front-loaded sentence that contains all necessary information without any filler or redundant phrasing.

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 read-only lookup with one well-documented parameter and a likely output schema, the description is fully sufficient and leaves no critical gaps for an agent to misuse it.

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 single id parameter is well-described with a range (1–731); the description adds no further semantic value to the parameter beyond what the schema provides.

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 uses a specific verb ('Get') and resource ('power statistics') and clearly qualifies by ID, distinguishing it from sibling tools like get_hero and get_biography.

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 makes clear it is for retrieving power statistics for a hero by ID, which implicitly suggests when to use it, though it does not explicitly mention alternatives when full hero data or biography is needed.

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.