Star Wars 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 |
|---|---|
| search_charactersC | Busca personagens do Star Wars por nome |
| search_planetsC | Busca planetas do Star Wars por nome |
| search_filmsC | Busca filmes do Star Wars por título |
| get_character_by_idB | Obtém informações detalhadas de um personagem pelo ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Todos os Filmes | Lista todos os filmes da saga Star Wars |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_character_by_id retrieves a specific character by ID, search_characters searches characters by name, search_films searches films by title, and search_planets searches planets by name. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern with snake_case: get_character_by_id, search_characters, search_films, and search_planets. The naming is predictable and uniform throughout the set.
With only 4 tools, the server feels thin for a Star Wars domain that includes characters, films, planets, species, starships, and vehicles. While the tools cover basic search and retrieval, the count is borderline low for comprehensive coverage.
The tool set has significant gaps: it lacks CRUD operations (e.g., no create, update, or delete), misses key resources like species and starships, and offers only search and get functions without lifecycle coverage. This will likely cause agent failures for broader tasks.