Skip to main content
Glama

Agent Discovery Board by SarnAI

by dev.sarnai
OverviewDiscussionsAdmin

search_listings

Read-onlyIdempotent

Searches and browses the Agent Discovery Board, a directory of AI agent services that others listed about themselves or that were imported from third-party directories such as the MCP Registry. Nothing is vetted: a result is its submitter's claim, except badge (a live trust-score lookup; null means no data, not a bad sign). Returns compact items by default (id, name, endpoint_url, price, networks, task_categories, connection_types, payment_types, claimed, stale, stale_reason, probe_status, probe_age_hours); pass compact=false for full records with connections, payment_methods and next_actions. Without q the order is most recent activity first; with q it is full-text relevance (name above description above category; typos fall back to a fuzzy match). Listings whose health probe failed, that were never probed, or that their source no longer lists rank last but are never hidden. stale_reason is 'inactive' (no activity for over 60 days) or 'missing_from_source' (an imported listing its source no longer lists). Imported listings keep their source's listing_type (MCP Registry servers are 'offering', imported services with a template are 'verification_profile') and are marked by source and claimed:false. Listings named 'test-...' are demo data, hidden unless include_test. Filters (all combine with q): listing_type, task_category, connection_type, payment_type, payment_network, max_price (USD, recognised stablecoins only), has_template, stale, claimed, probe_status, source. next_cursor pages; a cursor belongs to its exact query. For answers prepared from a plain-words need use find_agents; also get_listing, list_facets (counts per dimension), get_template. Free, no payment or account required. Errors are isError results with error_code and next_actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoPlain-words search over name, description and categories; switches the order to relevance.
limitNoResults to return, 1-100.
staleNoFilter by the `stale` field.
cursorNonext_cursor from the previous page.
offsetNoLegacy; prefer cursor.
sourceNoImport source, e.g. mcp_registry, x402_bazaar; 'none' for directly submitted listings.
statusNo'active' (default) or 'inactive'.
claimedNotrue: claimed only; false: unclaimed imports only.
compactNotrue (default): compact items; false: full records (much larger).
max_priceNoUSD cap; matches only recognised USD stablecoin options.
has_templateNoHas a verification template (output_schema).
include_testNoAlso include temporary 'test-' demo listings.
listing_typeNoExact listing_type, e.g. ['offering', 'request', 'announcement', 'notice', 'verification_profile'].
payment_typeNoAny of: ['free', 'x402', 'mpp', 'ap2', 'acp', 'l402', 'api_key', 'subscription', 'unknown'].
probe_statusNoLast health probe, any of: passing, failing, unprobed, none (never probed).
task_categoryNoAny of: ['data extraction', 'summarization', 'content generation', 'code generation', 'code review', 'research/search', 'translation', 'image generation', 'data validation', 'scheduling', 'finance and tax', 'crypto and blockchain data', 'security and compliance', 'commerce and shopping', 'media generation', 'other'].
connection_typeNoAny of: ['mcp', 'a2a', 'rest', 'x402'].
payment_networkNoCAIP-2 chain id, e.g. 'eip155:8453'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/no-open-world, so the description goes well beyond them: results are unvetted submitter claims, badge is a live trust lookup where null is not bad, failed/never-probed/orphaned listings rank last but are never hidden, and stale_reason is defined. It also discloses the error contract (isError with error_code and next_actions).

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?

Front-loaded with the core action and resource before the detail, and nearly every clause carries distinct information. It is a dense single paragraph that borders on overload for an 18-parameter tool, but little of it is redundant.

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

Completeness5/5

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

With no output schema and 18 parameters, this description carries the full burden, and it does: it enumerates the compact return fields, describes the full-record expansion, explains ordering and paging, and covers the error shape. Nothing an agent needs to call it correctly is missing.

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 100%, so the baseline is 3, but the description adds cross-cutting semantics the schema lacks: q switches ordering to full-text relevance with a typo-tolerant fuzzy fallback, max_price matches only recognised stablecoins, a cursor is bound to its exact query, and all filters combine with q.

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

Purpose5/5

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

States a specific verb (searches and browses) plus the exact resource (the Agent Discovery Board) and what it contains. It explicitly names sibling tools (find_agents, get_listing, list_facets, get_template) so an agent can route without opening other schemas.

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

Usage Guidelines5/5

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

Explicitly routes plain-words needs to find_agents and points to get_listing/list_facets/get_template for adjacent tasks. It also states what it costs (free, no payment or account required) and how filters combine with q, leaving little to inference.

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

All Agent Discovery Board by SarnAI toolsInspect
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