mcp-agno
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 |
|---|---|
No tools | |
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 3 tools
Each tool has a clearly distinct purpose: get_agno_page retrieves specific page content, list_agno_sections enumerates available sections, and search_agno_docs performs keyword searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with 'agno' as a prefix (get_agno_page, list_agno_sections, search_agno_docs). This uniformity enhances readability and predictability across the toolset.
With 3 tools, the count is slightly low but reasonable for a documentation-focused server. It covers core operations (fetch, list, search), though additional tools like update or delete might be expected in a broader CRUD context, but are unnecessary here given the domain.
The toolset provides complete coverage for interacting with AGNO documentation: listing sections, fetching specific pages, and searching content. There are no obvious gaps for the stated purpose, and agents can perform typical documentation workflows without dead ends.