Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

serebii_pokemongo_event_detail_global

Retrieve the public tables from a Serebii Pokémon GO Global Events detail page by filename, without fetching linked pages or media.

Instructions

Get a Serebii Pokémon GO global event page. Returns the public tables from one native Global Events detail page. Linked pages and media are not fetched.

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": {
      "filename": "<filename>"
    },
    "name": "serebii_pokemongo_event_detail_global"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesNative event page filename returned by the Global Events list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does add real scope information — only public tables from a single native page are returned, and linked pages and media are deliberately not fetched — but says nothing about access requirements, rate limits, or failure behavior for an invalid filename.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and immediately followed by the return scope and its limits. The second sentence slightly restates the first's resource, but there is no padding or filler.

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 one-parameter fetch tool with no output schema, the description covers what is returned (public tables) and what is not (linked pages, media), which is what an agent needs to decide whether this tool suffices. Only the absence of any guidance on sibling selection keeps it below full marks.

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 parameter already documents that it is a native event page filename from the Global Events list. The description repeats that provenance rather than adding format, validity, or example details, so it meets the baseline without exceeding it.

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?

The description gives a specific verb and resource: get a Serebii Pokémon GO global event page, returning the public tables from one native Global Events detail page. The word 'global' plus 'native ... detail page' implicitly separates it from the sibling detail tools (community day, raid day, hatch day, etc.), though it never names them 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: the filename parameter is described as coming from the Global Events list, which lightly routes the agent through the list tool first. There is no explicit statement of when to pick this detail tool over the other event detail siblings, and no exclusions or prerequisites are spelled out.

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

Deploy Server

Other Tools