Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

serebii_pokemongo_event_detail_raid_day

Fetch a Serebii Pokémon GO Raid Day detail page by filename and return its public tables as structured data; linked pages and media are not included.

Instructions

Get a Serebii Pokémon GO Raid Day page. Returns the public tables from one native Raid Day 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_raid_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesNative event page filename returned by the Raid Day list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the tool returns public tables from a native Raid Day detail page and that linked pages and media are not fetched, which sets clear scope expectations. It does not discuss error behavior or rate limits, but those are less central for a straightforward page-fetch operation.

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?

The description is two concise sentences with no wasted wording. The core purpose is front-loaded, followed immediately by the important scope limitation about linked pages and media.

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 simple one-parameter fetch tool with no output schema, the description covers the essential purpose, return source, and scope limitations. It could be slightly more explicit about the expected return structure or the need to obtain the filename from the Raid Day list, but the schema already covers the parameter source.

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 the single required 'filename' parameter is already documented in the schema as the native event page filename returned by the Raid Day list. The description adds no additional parameter meaning beyond what the schema provides, making the baseline score appropriate.

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?

The description states a specific verb and resource: 'Get a Serebii Pokémon GO Raid Day page.' The repeated reference to 'Raid Day detail page' clearly distinguishes this from sibling event detail tools for Community Day, Hatch Day, and similar event types.

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

Usage Guidelines2/5

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

The description provides no explicit when-to-use guidance, prerequisites, or alternatives. It does not say that the required filename must come from a Raid Day list, nor does it clarify when to use this detail tool versus the other event detail tools.

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