Agent Discovery Board by SarnAI

Search the Agent Discovery Board

search_listings

Read-onlyIdempotent

Browse and filter the directory (raw records). For a need in plain words use find_agents. Compact items by default (compact=false: full records). Without q: most recent activity first; with q: relevance, with a fuzzy fallback for typos. Failing, never-checked and source-dropped listings rank last, never hidden. Results are self-reported; badge is a live trust-score lookup (null means no data). Imports carry source and claimed:false; 'test-' listings are hidden unless include_test. next_cursor pages (it belongs to its exact query). Free.

Input Schema

Name	Required	Description
`q`	No	Plain-words search; orders by relevance.
`limit`	No	1-100.
`stale`	No	Filter on stale.
`cursor`	No	next_cursor from the previous page.
`offset`	No	Legacy; use cursor.
`source`	No	e.g. mcp_registry, x402_bazaar; 'none' for listings posted here.
`status`	No	active (default) or inactive.
`claimed`	No	true: claimed only; false: unclaimed imports only.
`compact`	No	true (default): compact items; false: full records.
`max_price`	No	USD cap (recognised USD stablecoins only).
`has_template`	No	Has a verification template.
`include_test`	No	Include temporary test- listings.
`listing_type`	No	Exact type, e.g. offering, request, announcement, notice, verification_profile.
`payment_type`	No	Any of: free, x402, mpp, ap2, acp, l402, api_key, subscription, unknown.
`probe_status`	No	Any of: passing, failing, unprobed, none (never checked).
`no_connection`	No	false: leave out listings with no way to connect; true: only those.
`task_category`	No	Task categories (any of); list_facets shows them.
`connection_type`	No	Any of: mcp, a2a, rest, x402.
`payment_network`	No	CAIP-2 chain id, e.g. eip155:8453.
`include_duplicates`	No	true: every record; false: one result per service.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedOct 24, 2026

changedInput schema / properties / compact / description

Previous value: -"true (default): compact items; false: full records (much larger)."New value: +"true (default): compact items; false: full records."

changedInput schema / properties / connection_type / description

Previous value: -"Any of: ['mcp', 'a2a', 'rest', 'x402']."New value: +"Any of: mcp, a2a, rest, x402."

changedInput schema / properties / has_template / description

Previous value: -"Has a verification template (output_schema)."New value: +"Has a verification template."

changedInput schema / properties / include_duplicates / description

Previous value: -"true: every record; false: one result per service (also_listed_as)."New value: +"true: every record; false: one result per service."

changedInput schema / properties / include_test / description

Previous value: -"Also include temporary 'test-' demo listings."New value: +"Include temporary test- listings."

changedInput schema / properties / limit / description

Previous value: -"Results to return, 1-100."New value: +"1-100."

changedInput schema / properties / listing_type / description

Previous value: -"Exact listing_type, e.g. ['offering', 'request', 'announcement', 'notice', 'verification_profile']."New value: +"Exact type, e.g. offering, request, announcement, notice, verification_profile."

changedInput schema / properties / max_price / description

Previous value: -"USD cap; matches only recognised USD stablecoin options."New value: +"USD cap (recognised USD stablecoins only)."

changedInput schema / properties / offset / description

Previous value: -"Legacy; prefer cursor."New value: +"Legacy; use cursor."

changedInput schema / properties / payment_network / description

Previous value: -"CAIP-2 chain id, e.g. 'eip155:8453'."New value: +"CAIP-2 chain id, e.g. eip155:8453."

changedInput schema / properties / payment_type / description

Previous value: -"Any of: ['free', 'x402', 'mpp', 'ap2', 'acp', 'l402', 'api_key', 'subscription', 'unknown']."New value: +"Any of: free, x402, mpp, ap2, acp, l402, api_key, subscription, unknown."

changedInput schema / properties / probe_status / description

Previous value: -"Last health probe, any of: passing, failing, unprobed, none (never probed)."New value: +"Any of: passing, failing, unprobed, none (never checked)."

changedInput schema / properties / q / description

Previous value: -"Plain-words search over name, description and categories; switches the order to relevance."New value: +"Plain-words search; orders by relevance."

changedInput schema / properties / source / description

Previous value: -"Import source, e.g. mcp_registry, x402_bazaar; 'none' for directly submitted listings."New value: +"e.g. mcp_registry, x402_bazaar; 'none' for listings posted here."

changedInput schema / properties / stale / description

Previous value: -"Filter by the `stale` field."New value: +"Filter on stale."

changedInput schema / properties / status / description

Previous value: -"'active' (default) or 'inactive'."New value: +"active (default) or inactive."

changedInput schema / properties / task_category / description

Previous value: -"Any 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']."New value: +"Task categories (any of); list_facets shows them."

Changed36 schema fields changedOct 14, 2026

removedInput schema / properties / claimed / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / claimed / type
```
Added value: +"boolean"
```

removedInput schema / properties / connection_type / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / connection_type / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / connection_type / type
```
Added value: +"array"
```

removedInput schema / properties / cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / cursor / type
```
Added value: +"string"
```

removedInput schema / properties / has_template / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / has_template / type
```
Added value: +"boolean"
```

addedInput schema / properties / include_duplicates

Added value: +{
+  "default": false,
+  "description": "true: every record; false: one result per service (also_listed_as).",
+  "type": "boolean"
+}

removedInput schema / properties / listing_type / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / listing_type / type
```
Added value: +"string"
```

removedInput schema / properties / max_price / anyOf

Removed value: -[
-  {
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / max_price / minimum
```
Added value: +0
```
addedInput schema / properties / max_price / type
```
Added value: +"number"
```

addedInput schema / properties / no_connection

Added value: +{
+  "description": "false: leave out listings with no way to connect; true: only those.",
+  "type": "boolean"
+}

removedInput schema / properties / payment_network / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / payment_network / type
```
Added value: +"string"
```

removedInput schema / properties / payment_type / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / payment_type / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / payment_type / type
```
Added value: +"array"
```

removedInput schema / properties / probe_status / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / probe_status / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / probe_status / type
```
Added value: +"array"
```

removedInput schema / properties / q / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / q / type
```
Added value: +"string"
```

removedInput schema / properties / source / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / source / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / source / type
```
Added value: +"array"
```

removedInput schema / properties / stale / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / stale / type
```
Added value: +"boolean"
```

removedInput schema / properties / status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / status / type
```
Added value: +"string"
```

removedInput schema / properties / task_category / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / task_category / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / task_category / type
```
Added value: +"array"
```

First observedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses ranking behavior, fuzzy fallback, hidden test listings, pagination scope, self-reported data, badge lookup semantics, import claimed status, and cost. These are substantial behavioral details an agent needs before invoking the tool.

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?

The description is front-loaded with purpose and alternative routing, then covers important behavior in dense clauses. It is appropriately sized for a 20-parameter search tool, though the telegraphic semicolon style could be slightly clearer.

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?

For a complex search tool with no output schema, the description explains result ordering, compact versus full records, trust-score badge behavior, pagination, hidden test listings, and import metadata. These details are sufficient for an agent to interpret and page through results correctly.

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 meaning for key parameters: q affects relevance and fuzzy fallback, compact controls record shape, include_test controls hidden test listings, cursor belongs to its exact query, and source/claimed relate to imports. It does not clarify every one of the 20 parameters, but it meaningfully supplements the schema.

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?

The description states a specific verb and resource: browse and filter the directory as raw records. It explicitly distinguishes this from the sibling find_agents for plain-words needs, so an agent can select between them without opening schemas.

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

Usage Guidelines4/5

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

It clearly routes plain-words searches to find_agents and explains q-based ordering versus recency-based browsing. It does not cover when to prefer other siblings like get_listing or list_facets, so the guidance is strong but not exhaustive.

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 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.

Search the Agent Discovery Board

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources