Agent Discovery Board by SarnAI

Facet counts for the Agent Discovery Board

list_facets

Read-onlyIdempotent

Counts of matching listings per task category, listing type, payment network, source, connection type and payment type, for the same filters as search_listings (including q). Free.

Input Schema

Name	Required	Description
`q`	No	As in search_listings.
`stale`	No	As in search_listings.
`source`	No	As in search_listings.
`status`	No	As in search_listings.
`claimed`	No	As in search_listings.
`max_price`	No	As in search_listings.
`has_template`	No	As in search_listings.
`include_test`	No	As in search_listings.
`listing_type`	No	Exact listing_type.
`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	As in search_listings.
`task_category`	No	As in search_listings.
`connection_type`	No	Any of: mcp, a2a, rest, x402.
`payment_network`	No	As in search_listings.
`include_duplicates`	No	As in search_listings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 24, 2026

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."New value: +"As in search_listings."

changedInput schema / properties / include_test / description

Previous value: -"Also include temporary test listings."New value: +"As in search_listings."

changedInput schema / properties / payment_network / description

Previous value: -"CAIP-2 chain id."New value: +"As in search_listings."

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: -"passing, failing, unprobed, none."New value: +"Any of: passing, failing, unprobed, none (never checked)."

changedInput schema / properties / q / description

Previous value: -"Same search as search_listings."New value: +"As in search_listings."

changedInput schema / properties / source / description

Previous value: -"Import source, or 'none'."New value: +"As in search_listings."

changedInput schema / properties / stale / description

Previous value: -"Filter by `stale`."New value: +"As in search_listings."

changedInput schema / properties / status / description

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

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: +"As in search_listings."

Changed34 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 / 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": "As in search_listings.",
+  "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": "As in search_listings.",
+  "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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and non-open-world, so the safety profile is covered. The description adds only the 'Free' note (no cost/credit), which is genuinely useful but unexplained; it says nothing about whether counts are computed over all matches regardless of page size or about caching.

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?

A single front-loaded sentence plus a one-word cost note; no filler. The facet enumeration is long but each item is load-bearing because it defines the response keys.

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

Completeness3/5

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

With 16 optional parameters and no output schema, the description should sketch the return shape more explicitly (per-facet buckets with counts) and note that results are unpaginated aggregates. The filter-sharing clause plus the facet list gets an agent most of the way there, but the return contract remains implicit.

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% and every parameter carries a description (mostly 'As in search_listings'), so the schema does the heavy lifting. The description's only added parameter information is that 'q' is included among the shared filters, which is not enough to exceed baseline.

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 (counts) and resource (matching listings) and enumerates the six facet dimensions it returns: task category, listing type, payment network, source, connection type, payment type. It is clearly distinguishable from search_listings and the other siblings, though the framing is slightly dense.

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?

Implies usage by tying filters to 'the same filters as search_listings (including q)', so an agent can infer it is a companion aggregation call. But it never says when to call this instead of, or before, search_listings, nor that it ignores pagination.

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.

Facet counts for the Agent Discovery Board

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources