Skip to main content
Glama
Sign In

PoGoBud

by com.pogobud
OverviewDiscussionsAdmin

Raid counters

raid_counters
Read-onlyIdempotent

Best counters for one raid boss, how many trainers it needs, its weaknesses and catch CP. boss is a Pokémon name or PoGoBud id (dialga, giratina-origin, mewtwo-mega-x, shadow-raikou).

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": {
      "boss": "<boss>"
    },
    "name": "raid_counters"
  }
}

Input Schema

NameRequiredDescriptionDefault
bossYesRaid boss name or id, e.g. 'dialga' or 'shadow raikou'
tierNoOnly the boss's usual tier is answered (the default); any other tier gets the boss page link instead. Leave it out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tier / description
      Previous value: -"Raid tier (1, 3, 4, 5, mega, mega_legendary, primal, shadow_1, shadow_3, shadow_5); default: the boss's usual tier"New value: +"Only the boss's usual tier is answered (the default); any other tier gets the boss page link instead. Leave it out."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world operation, lowering the bar. The description adds the useful behavioral fact that non-default tiers short-circuit to a page link, but it says nothing about failure modes for unknown boss names or the shape/size of the counter list.

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: the first front-loads what the tool returns, the second front-loads the required parameter and its accepted formats. No filler, no restatement of the title.

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?

For a two-parameter, single-boss lookup with no output schema, listing the returned fields and the boss id formats makes the definition self-sufficient. The only gap is that it never discourages or explains use of the tier parameter, leaving that entirely to the schema.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns a bump by supplying slug-format examples beyond the schema's ('giratina-origin', 'mewtwo-mega-x', 'shadow-raikou'), clarifying that hyphens and shadow/mega prefixes are acceptable ids. It does not explain the tier parameter, but the schema covers that fully.

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 concrete verb-resource pairing ('Best counters for one raid boss') and enumerates the payload (counters, trainers needed, weaknesses, catch CP), so the agent knows exactly what it gets back. It scopes itself to a single boss, which implicitly separates it from the plural-looking sibling max_counters, but never names that sibling explicitly.

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?

Usage is only implied: 'for one raid boss' suggests a pre-raid prep scenario, but there is no explicit when-to-use, no when-not, and no pointer to max_counters, pokemon_info, or raids_now. The one piece of real routing guidance (non-default tiers return a link instead) lives in the schema, not the description.

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

All PoGoBud toolsInspect
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.

Resources