Skip to main content
Glama

Search AI agents

search_agents
Read-only

Find AI agents, MCP servers and agent tools that do a job. Describe the task in plain words (e.g. 'reply to customer emails for a dental clinic'). Optional filters narrow by industry, type, price, setup and integration. Results come from the AgentExplorio index with verification labels; unverified listings are labeled.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
priceNo
queryYesWhat you need done
setupNo
industryNoIndustry slug, e.g. legal, healthcare, ecommerce-retail
works_withNoIntegration or protocol, e.g. Slack, HubSpot, WhatsApp, MCP
verified_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: results come from the AgentExplorio index and carry verification labels, with unverified listings explicitly labeled, which tells the agent how to weigh trust in results. It omits ranking, ordering, and what happens when nothing matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action, then usage, then filters, then result provenance. The closing clause about unverified listings partially repeats the earlier 'verification labels' mention, which is the only wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter search with no output schema, the description covers purpose, query phrasing, filter scope, and result provenance adequately. It could still say more about result volume (limit default 8, max 20) and what a result record contains, since no output schema exists to carry that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 38%, so the description must compensate, and it does: it maps the filter concepts to plain language (industry, type, price, setup, integration) and gives a concrete natural-language example for the required query. It still leaves 'limit' and the exact semantics of 'verified_only' unaddressed beyond the verification-label remark.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb plus the exact resource set ('Find AI agents, MCP servers and agent tools that do a job'), which is more precise than the title alone. It does not explicitly differentiate itself from siblings like get_agent or compare_agents, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent how to phrase the required query ('Describe the task in plain words') with a worked example, and notes that filters are optional narrowing aids. However, it gives no when-not-to-use guidance and never points to compare_agents or get_agent for lookup or comparison tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources