Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

serebii_pokemongo_event_detail_ticket

Fetches a Serebii Pokémon GO ticket event detail page by filename and returns its public tables, excluding linked pages and media.

Instructions

Get a Serebii Pokémon GO ticket event page. Returns the public tables from one native Ticket 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_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYesNative event page filename returned by the Ticket Events 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 supplied, the description carries the full burden and does useful work: it discloses that only 'public tables from one native Ticket Events detail page' are returned and that 'Linked pages and media are not fetched', preventing an agent from expecting crawler-style expansion. It stops short of covering failure behavior on an invalid filename or any rate/access constraints.

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 action, then the return scope, then the exclusion. Every sentence contributes new information and there is no 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, no-output-schema fetch tool, the definition tells the agent what to pass, where that value originates, and what the response body conceptually contains plus what it omits. Only edge-case behavior (invalid filename, empty results) is left 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 coverage is 100% and the single filename parameter is already documented as 'Native event page filename returned by the Ticket Events list'. The description repeats the upstream-source idea without adding format, examples, or error semantics, so it meets but does not exceed the baseline.

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 ('Get a Serebii Pokémon GO ticket event page') and scopes it to 'one native Ticket Events detail page', which separates it from the other event_detail_* siblings covering community days, raids, research days, etc. It doesn't explicitly name those alternatives, so the differentiation is implicit rather than stated.

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 argument description says the filename comes 'from the Ticket Events list', which suggests the list-then-detail workflow, but the description itself gives no explicit when-to-use or when-not-to-use guidance and names no alternatives.

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