Pokemon Paste MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_pokepasteC | Create a Pokepaste from Pokemon set data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as creating Pokepastes from Pokemon set data, making it distinct by default.
The single tool name follows a clear verb_noun pattern (create_pokepaste), which is consistent and predictable. There are no other tools to compare against, so naming conventions cannot be inconsistent.
A single tool is too few for a server that appears to handle Pokemon paste creation, as it lacks essential operations like retrieving, updating, or deleting pastes. This minimal scope limits functionality and suggests an incomplete surface for the domain.
The server is severely incomplete, offering only creation without any read, update, or delete capabilities. This creates significant gaps, as agents cannot manage or access existing pastes, leading to potential dead ends in workflows.