Skip to main content
Glama

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.

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_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoPlain-words search; orders by relevance.
limitNo1-100.
staleNoFilter on stale.
cursorNonext_cursor from the previous page.
offsetNoLegacy; use cursor.
sourceNoe.g. mcp_registry, x402_bazaar; 'none' for listings posted here.
statusNoactive (default) or inactive.
claimedNotrue: claimed only; false: unclaimed imports only.
compactNotrue (default): compact items; false: full records.
max_priceNoUSD cap (recognised USD stablecoins only).
has_templateNoHas a verification template.
include_testNoInclude temporary test- listings.
listing_typeNoExact type, e.g. offering, request, announcement, notice, verification_profile.
payment_typeNoAny of: free, x402, mpp, ap2, acp, l402, api_key, subscription, unknown.
probe_statusNoAny of: passing, failing, unprobed, not_checked, none (never checked).
no_connectionNofalse: leave out listings with no way to connect; true: only those.
task_categoryNoTask categories (any of); list_facets shows them.
connection_typeNoAny of: mcp, a2a, rest, x402.
payment_networkNoCAIP-2 chain id, e.g. eip155:8453.
include_duplicatesNotrue: every record; false: one result per service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / probe_status / description
      Previous value: -"Any of: passing, failing, unprobed, none (never checked)."New value: +"Any of: passing, failing, unprobed, not_checked, none (never checked)."
  2. Changed17 schema fields changed
    • 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."
  3. Changed36 schema fields changed
    • 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"
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent profile, so the description carries the rest: ranking rules (failing, never-checked and source-dropped listings rank last but are never hidden), that results are self-reported, that badge is a live trust-score lookup returning null when no data exists, and that the tool is free. This is real behavioral context beyond what structured fields declare.

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 and waste-free — every clause carries a distinct fact. The telegraphic, semicolon-chained style is dense and takes effort to parse, but nothing is filler.

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 20-parameter tool with no output schema, the description still conveys return shape (compact items vs full records, self-reported fields, nullable badge) and pagination semantics. Remaining gaps are minor since the schema fully documents the filters.

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; the description still adds meaning by tying cursor to its originating query, explaining that compact controls compact-vs-full records, and clarifying that claimed/source reflect imported records. It does not touch the many filter params (probe_status, payment_type, etc.), but the schema documents those well.

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 and resource ("Browse and filter the directory (raw records)") and immediately distinguishes itself from the sibling it is not: "For a need in plain words use find_agents." An agent can pick between search_listings and find_agents without opening either schema.

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?

Explicit routing rule to find_agents for natural-language needs, plus conditions for the default compact view, the q/no-q ordering switch, and include_test for 'test-' listings. It also warns that next_cursor belongs to its exact query, which is a usage constraint an agent would otherwise get wrong.

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.