Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

serebii_pokemongo_event_only_moves

Retrieve Serebii Pokémon GO event-only move tables with Fast Attacks and Charge Attacks for moves identified as event-exclusive.

Instructions

List Serebii Pokémon GO event-only move tables. Returns Serebii's Fast Attacks and Charge Attacks tables for moves identified as event-only.

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_event_only_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the return content (Fast Attacks and Charge Attacks tables for event-only moves), which is genuinely useful, but it omits safety profile, auth or rate-limit behavior, and whether the result is static or refreshed, leaving a mutation-free read tool under-described.

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?

Two tight sentences with no filler, and the core scope statement is front-loaded ahead of the return-value detail. Every sentence earns its place.

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 zero-parameter, read-only listing with no output schema, the description covers what the tool is and what it returns, which is most of what an agent needs. It stops short of stating access constraints or the freshness of the Serebii tables, but the gaps are minor given the tool's simplicity.

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 no parameter semantics for the description to compensate for; the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

Uses a specific verb ("List") with a concrete resource ("Serebii Pokémon GO event-only move tables") and clarifies the contents as event-only moves. It does not, however, distinguish itself from the sibling tools in the serebii_pokemongo family (e.g. event_only_research), so an agent must infer the boundary from the name alone.

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?

The scope word "event-only" implicitly tells the agent when this table applies, but there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as the research or categories siblings. Usage is inferable but not stated.

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