FindAgent
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_agentsA | Search FindAgent's public catalog of vetted MCP "doer" agents (coding, data analysis, customer support, design, DevOps, and more). Returns matching agents with slug, title, tagline, and description. Read-only, no auth. |
| get_overviewA | Get a machine-readable overview of FindAgent — what it is, how to connect, and the key public routes. Read-only, no auth. |
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
The two tools have clearly separate purposes: one searches the agent catalog, the other provides an overview of the service itself. There is no overlap or ambiguity in what each tool is for.
Both tool names follow the same verb_noun snake_case pattern: search_agents and get_overview. The naming is consistent, predictable, and readable.
With only two tools, the surface feels thin for a public agent catalog. The tools are useful, but the low count makes the server feel minimal rather than fully featured.
The core search capability is present, but there is no obvious way to retrieve a specific agent by slug, list agents without a query, or browse by category. The overview endpoint is meta-information rather than a domain operation, leaving some discovery workflows incomplete.