VGC Teambuilder

Compare usage between two months

get_meta_shifts

Read-onlyIdempotent

Compare a regulation's usage between two months: the biggest risers and fallers, Pokémon that newly reached meaningful usage and Pokémon that dropped out. Use it to see how the metagame changed. Needs at least two months of history.

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": "get_meta_shifts"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last month, YYYY-MM. Defaults to the most recent month
`from`	No	First month, YYYY-MM. The nearest month with data is used if it has none
`limit`	No	Maximum entries to return (1–25). Defaults to 10
`format`	No	Regulation id from list_formats. Defaults to "champions-regmc" (Pokémon Champions — Regulation M-C).
`months`	No	Months to look back from `to` when `from` is omitted. Defaults to 3

Output Schema

Name	Required	Description
`to`	Yes	Last month compared, YYYY-MM
`from`	Yes	First month compared, YYYY-MM
`format`	Yes	Regulation id the result applies to
`risers`	Yes
`fallers`	Yes
`dropouts`	Yes
`formatName`	Yes	Display name of the regulation
`newEntrants`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description usefully adds a data-availability precondition, but does not say what happens when that precondition fails (error vs. empty result), and it omits that omitted month arguments fall back to defaults — a behavior only the schema reveals.

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?

Three short sentences: what it returns is front-loaded, the purpose follows, and the prerequisite closes. Every sentence earns its place with no redundancy.

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 an output schema present, the description needn't explain return values, and rich annotations plus full schema coverage carry the mechanics. It supplies purpose, output scope and a precondition — sufficient for correct invocation, with only the insufficient-history behavior left unspecified.

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 description coverage is 100%, so all five parameters (to, from, limit, format, months) are already documented with patterns, ranges and defaults. The description only gestures at 'two months' and 'biggest risers and fallers' (limit), adding essentially nothing beyond the schema; baseline 3 applies.

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 ('Compare a regulation's usage between two months') and enumerates the output shape: biggest risers/fallers, newcomers, and dropouts. That output framing distinguishes it from generic trend siblings, though no sibling is named explicitly.

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?

Gives a clear use case ('see how the metagame changed') and a stated prerequisite ('Needs at least two months of history'), which is real routing information. It does not, however, contrast itself against the neighboring get_usage_trend or get_usage_momentum tools, so the alternative-selection guidance is implicit.

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.