squadco-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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_docsA | List all available SquadCo API documentation files. |
| search_docsB | Search for documentation sections by title or summary. Use this when you aren't sure where a specific feature (e.g. "AES encryption") is documented. |
| get_doc_structureB | Get the structure/nodes of a specific document. Use this to see what sections are available before resolving. |
| resolve_sectionA | Fetch the full content of a specific documentation section. Provide the doc_id (e.g. 'payments') and the section_id (e.g. 'standard-test-cards'). |
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 4 tools
Each tool has a distinct role: listing all docs, getting a doc's structure, fetching a section's content, and searching by title/summary. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (list_docs, get_doc_structure, resolve_section, search_docs), making them predictable and easy to understand.
With 4 tools, the surface is concise. It covers the essential documentation tasks (list, search, browse structure, fetch content) without being too sparse or overengineered.
The tool set covers navigation and retrieval of documentation. A minor gap is the lack of a tool to fetch an entire document in one call, but this can be worked around by iterating sections.