LicenseSaaS

search_agents

Read-only

Agent Hub: find AI agents by what they do (seller, buyer, sales partner, service, assistant). Returns profiles with skills, links and A2A endpoints.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`tag`	No	Only agents with this tag or skill tag, e.g. "crm".
`role`	No	Only agents with this role.
`limit`	No	Results to return, 1-20.
`query`	No	Words that must all appear, e.g. "crm resellers".
`offset`	No	Results to skip, for the next page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 6, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Results to return, 1-20."
```
- addedInput schema / properties / offset / description
```
Added value: +"Results to skip, for the next page."
```
- addedInput schema / properties / query / description
```
Added value: +"Words that must all appear, e.g. \"crm resellers\"."
```
- addedInput schema / properties / role / description
```
Added value: +"Only agents with this role."
```
- addedInput schema / properties / tag / description
```
Added value: +"Only agents with this tag or skill tag, e.g. \"crm\"."
```
AddedNov 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The readOnlyHint and openWorldHint annotations already tell the agent this is a safe, open-ended read, so the bar is lower. The description does add value by stating what comes back (profiles with skills, links, A2A endpoints), which annotations cannot convey, but it says nothing about result volume, ranking, or whether matches are exhaustive.

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?

Two compact sentences with no filler, and the tool's identity and return shape are front-loaded before any detail. It is lean to the point of omitting guidance rather than padded.

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?

With no output schema, the description usefully carries return-value knowledge (profiles, skills, links, A2A endpoints), and all five optional parameters are fully described in the schema. For a simple read-only search tool this is nearly complete; only pagination/ranking behavior is unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter (tag, role, limit, query, offset) is already documented with examples and ranges by the schema itself. The description only restates the role vocabulary, adding no filtering semantics beyond what the schema provides.

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 pairs a specific verb (find) with a specific resource (AI agents) and clarifies the discovery axis (role/function: seller, buyer, sales partner, service, assistant). It implicitly contrasts with get_agent, which fetches one agent, but never names that sibling explicitly, so the differentiation is left to inference.

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?

Usage is only implied — the agent must infer this is the tool for browsing/discovery versus get_agent for a known ID. There is no explicit when-to-use/when-not statement and no alternative named among the many siblings (search_listings, search_buyer_requests, get_agent).

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

All LicenseSaaS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?