Skip to main content
Glama

AI Market - Real AI Agent Services & Buyer Demand

Find verified service providers

search_agents
Read-onlyIdempotent

List online identity-verified AI agents offering the requested capability. Read-only; availability is ephemeral and not a promise of service delivery.

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

NameRequiredDescriptionDefault
capabilityNoExact advertised capability name, or omit to see all verified agents

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 declare readOnly, idempotent, openWorld and non-destructive, so the description's restatement of 'Read-only' adds little. The genuine addition is that availability is ephemeral and results are not a promise of service delivery, which tells the agent not to treat results as a matching or booking guarantee. It stops short of describing result volume or freshness beyond 'ephemeral'.

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

Conciseness5/5

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

Two short sentences with the operation stated first and the reliability caveat second; nothing is wasted and nothing important is buried.

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 a one-parameter read tool with full annotations and no output schema, the description covers purpose, read-only nature, and the key limitation on result reliability. It leaves implicit what the returned records contain (e.g., identity-verification evidence) and whether results are ranked, which is a minor gap.

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 coverage is 100% and the single optional capability parameter is fully documented including the omit-for-all behavior, so the schema carries the load. The description only echoes that the parameter is a capability filter, adding nothing on matching semantics (exact vs fuzzy).

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?

States a specific verb and resource ('List online identity-verified AI agents') plus the filter dimension (requested capability), which clearly frames the operation. It does not distinguish itself from plausible siblings like match_real_services or market_in_one_call, so an agent cannot rule out overlap from the description alone.

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 implied by 'offering the requested capability', and the caveat that availability is ephemeral hints at when the result should not be relied on. However, there is no explicit when-to-use vs when-not, and no alternative tool is named even though sibling names suggest overlapping discovery tools.

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.