Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

serebii_pokemongo_event_detail_community_day

Fetch structured tables from a Serebii Pokémon GO Community Day detail page using its native filename, so you can extract event details without fetching linked pages or media.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
filenameYesNative event page filename returned by the Community Day list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden, and it does useful work: it states the tool returns "public tables" from a native detail page and that "linked pages and media are not fetched," which sets real expectations about fetch depth and recursion. It still omits failure behavior (e.g. what happens on an unknown filename) and does not explicitly confirm read-only semantics, so it stops short of a 5.

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, front-loaded with the resource and immediately followed by the return scope and the exclusion. Every sentence adds distinct information and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter fetch tool this is close to adequate, but there is no output schema, so the description should say more about the shape of the returned tables. "Public tables" is a hint rather than a description, and error behavior on a bad filename is unaddressed.

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%, and the parameter already documents that it is a native event page filename returned by the Community Day list. The description adds no format, case, or example guidance for that filename. With the schema doing the work, this is the baseline 3.

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 names a specific verb and resource: "Get a Serebii Pokémon GO Community Day page," then narrows the scope to "one native Community Day detail page." This clearly separates it from the other event-type detail siblings (hatch_day, raid_day, research_day) without having to name them. It is not quite a 5, because it never explicitly points to an alternative for non-Community-Day pages.

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 schema note says the filename comes "from the Community Day list," which hints that the list tool runs first. The description gives no explicit when-to-use or when-not-to-use guidance and does not name a sibling alternative. A reader can infer the sequence but must supply it themselves.

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