random-pokemon-mcp

analyze_team

Read-only

Analyze 1–6 Showdown sets to identify defensive weaknesses, learnable damaging-move type coverage, base-speed tiers, and evidence gaps across PokeAPI version groups.

Instructions

Analyze 1–6 Showdown sets: defensive weaknesses, learnable damaging-move type coverage, base-speed tiers and evidence gaps. Across all PokeAPI version groups; no submitted-move or current-format legality verification.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "analyze_team"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds meaningful context beyond that: the analysis spans all PokeAPI version groups and explicitly does not verify submitted-move or current-format legality, which is an important limitation an agent should know.

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?

Two tightly written sentences, front-loaded with the core action and scope, with no wasted words. Every clause adds either capability or a limitation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and a read-only analysis tool, the description usefully enumerates the categories of analysis returned (weaknesses, coverage, speed tiers, evidence gaps) and clarifies legality limits. It could be stronger by describing the expected input format for the lone 'text' parameter.

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 0%, so the description must carry parameter meaning. It partially compensates by revealing that the single 'text' parameter should contain 1–6 Showdown sets, but it does not explain the expected text format, delimiter conventions, or what a valid Showdown set looks like.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Analyze 1–6 Showdown sets') and enumerates the outputs (defensive weaknesses, type coverage, base-speed tiers, evidence gaps), making its function clear. It does not explicitly contrast itself with siblings like calc_damage or get_type_effectiveness, but the team-level scope is distinctive enough.

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

Usage Guidelines3/5

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

The description implies usage for team analysis and gives useful scope boundaries ('Across all PokeAPI version groups; no submitted-move or current-format legality verification'), but it never states when to choose this tool over alternatives or what prerequisites the input needs.

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

Deploy Server