agentready-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTREADY_MCP_URL | No | Override the MCP endpoint (for self-hosted) | https://www.agentready.it.com/api/mcp |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List all websites indexed by AgentReady that can be queried with ask_site. Returns domain, title, summary, and page count for each site. |
| ask_siteA | Ask a question about any website indexed by AgentReady and get a cited answer grounded in that site's actual content. First call list_sites to see which domains are available. |
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 2 tools
ask_site and list_sites have clearly distinct purposes: one lists available sites, the other queries a specific site's content. There is no overlap.
Both tool names follow a consistent verb_noun pattern (list_sites, ask_site) and use snake_case.
With only 2 tools, the server is minimal but covers the core workflow (discovery and query). It feels slightly thin but acceptable for a narrow domain.
The tool surface covers the primary tasks: discovering indexed sites and asking questions about them. Minor missing features like pagination for list_sites or site detail, but no dead ends.