Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

serebii_pokemongo_events

Fetch event rows from a Serebii Pokémon GO category page, preserving source order and date labels to support Pokémon GO event tracking.

Instructions

List events from a Serebii Pokémon GO category page. Returns the rows from one native Serebii Pokémon GO event category page, preserving source order and date labels.

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": {
      "category": "<category>"
    },
    "name": "serebii_pokemongo_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesNative event page filename from event-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that output preserves source order and date labels and is scoped to a single page, but it says nothing about network/fetch behavior, error handling for an unexpected category, or whether results are cached or live-scraped.

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?

Two short sentences with the scope stated first. The second sentence partly restates the first ('Returns the rows from one native ... page') but earns its place by adding source order and date-label preservation.

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?

There is no output schema, so the description must convey the return shape; it says 'rows' with date labels but never describes what a row contains (event name, dates, link to detail) or how many rows/pagination behaves. For a simple one-parameter listing tool this is adequate but leaves a real 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?

Schema coverage is 100% and the single enum parameter already documents itself as the 'Native event page filename from event-categories'. The description reinforces that 'category' selects one native page but adds no format detail (e.g., whether the '.shtml' suffix is required) 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?

The description uses a specific verb ('List') and resource ('events from a Serebii Pokémon GO category page'), and the second sentence clarifies the scope as exactly one native category page. It does not explicitly name the distinction from serebii_pokemongo_event_categories (which supplies the page filenames) or the event_detail_* siblings, so it falls short of 5.

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?

There is no explicit when-to-use or when-not-to-use guidance. An agent can infer this is the listing-level tool and that detail siblings exist, but the description never states the condition that selects this tool over event_categories or the event_detail_* tools, and it does not state that 'category' values come from serebii_pokemongo_event_categories.

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