ParrotPod MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsA | Search ParrotPod documentation for specific technical information, setup guides, or feature details. |
| get_full_documentationB | Retrieve all ParrotPod documentation at once. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ParrotPod Master Documentation (Markdown) |
TDQS
Scored across 2 tools
search_docs and get_full_documentation have clearly distinct purposes: one retrieves specific information via search, the other returns all documentation in one call. No ambiguity between the two.
Both tool names follow a consistent verb_noun pattern ('search' + object, 'get_full' + object), making the naming predictable and uniform.
With only 2 tools, the set feels minimal, but for a documentation-specific server this scope is reasonable and not excessive. It is slightly thin but appropriate for the narrow domain.
The tool surface covers the two primary ways to access documentation: targeted search and full retrieval. Minor gaps exist, such as a tool for fetching a specific section by ID, but the core needs are met.