Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

serebii_pokemongo_event_detail_hatch_day

Retrieve public tables from a Serebii Pokémon GO Hatch Day detail page using its native filename; linked pages and media are not fetched.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
filenameYesNative event page filename returned by the Hatch 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?

With no annotations, the description does real work by disclosing scope of return: public tables only, from the single native page, with linked pages and media explicitly excluded. It leaves unaddressed error behavior for a bad filename and whether the page content is fetched live, but the key expectation-setting is present.

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: identity first, payload second, exclusion third. No filler and no repetition of the tool name as a restatement of purpose.

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, read-only scrape of a single page with no output schema, the description covers what is returned and what is deliberately omitted. A little more on what 'public tables' contain, or failure behavior for an unknown filename, would close the remaining gap.

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?

There is a single parameter with 100% schema description coverage that already explains 'filename returned by the Hatch Day list.' The description adds no syntax, format, or validity detail beyond the schema, so the 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: fetch one native Hatch Day detail page from Serebii Pokémon GO. The event-type qualifier ('Hatch Day') implicitly separates it from the Community Day, Raid Day, Research Day siblings, though the description never names an alternative to route against.

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 tool is the detail-fetch counterpart to a Hatch Day list, and the filename prerequisite lives in the schema's parameter description rather than the tool description. There is no explicit when-to-use versus other event-detail tools, and no statement about when not to call it.

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