VGC Teambuilder

List supported formats

list_formats

Read-onlyIdempotent

List the Pokémon Champions regulations this connector supports, with each one's id, dates, whether it is current, team rules, number of legal Mega Evolutions and whether usage statistics are available. Use it to find the format value other tools accept and to see which format they use by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_formats"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`formats`	Yes
`defaultFormat`	Yes	Format used when a tool's `format` is omitted

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description goes beyond them by enumerating what each entry carries (id, dates, current flag, team rules, legal Mega Evolutions, usage-stat availability) and by noting a default-format behavior the agent would otherwise have to discover empirically.

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 sentences, front-loaded with the resource and followed by the concrete fields returned and the discovery purpose. No filler and no restatement of the title.

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 no-argument, read-only discovery tool with an output schema present, the description covers purpose, the actionable takeaway (`format` id), and enough of the payload shape to know what a caller gets. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Zero parameters, so the baseline is 4; there is nothing parameter-level for the description to explain, and it correctly frames the output's `format` value as the input other tools need.

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?

States a specific verb and resource (list the Pokémon Champions regulations this connector supports) and immediately ties it to the `format` identifier other tools consume, which separates it from every sibling, none of which enumerate formats.

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?

Explicitly says when to use it: to discover the `format` value other tools accept and to learn the default format. That is clear routing guidance; it does not name exclusions or alternatives, but for a zero-parameter discovery tool the intended use is unambiguous.

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

All VGC Teambuilder 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.