Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

serebii_pokemongo_unown_events

Retrieve Serebii Pokémon GO Unown event location rows, including source date, event, locations, letters, and restrictions, to check where and when Unown variants appeared.

Instructions

List Serebii Pokémon GO Unown event locations. Returns the rows from Serebii's Unown Event Locations archive, including source date, event, locations, letters, and restrictions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "serebii_pokemongo_unown_events"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the return shape (source date, event, locations, letters, restrictions), which substitutes somewhat for a missing output schema, but says nothing about read-only nature, data freshness/caching, pagination, or error behavior.

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 sentences, front-loaded with the action and resource, with no filler. There is mild redundancy between 'List ... event locations' and the later 'including ... locations', but the return-field enumeration earns its space given no output schema.

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 no-parameter, read-only listing tool with no output schema, the description covers what it does and what the rows contain, which is enough to call it confidently. Only secondary operational details like data recency or result size limits are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; a no-argument listing tool is inherently simple to invoke. No parameter-level meaning is missing.

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 states a concrete verb (list) plus resource (Serebii Pokémon GO Unown event locations) and enumerates the row fields returned, so an agent can tell this is a dedicated Unown archive rather than the general event feed. It does not explicitly name the general sibling event tool it differs from, which keeps it below a 5.

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: an agent must infer that this tool is for Unown-specific event/location data and that the general event tools cover everything else. There is no explicit when-to-use, when-not-to-use, or alternative named in the text.

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