StealthStack ARD Discovery

Search discovered agentic resources

search_resources

Read-onlyIdempotent

Search the StealthStack ARD index for agentic resources (agents, MCP servers, skills, catalogs) discovered across the open web. Free-text query over name/description/tags, ranked by the index's relevance score (best match first). Optionally filter by kind, domain, trust, or accepted payment protocol (paid=x402). Each result includes the connect URL when the publisher provides one; otherwise the inline connection or pull details.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	No	Restrict to one resource kind.
`paid`	No	Only services that list this payment protocol (x402: pay-per-request in stablecoins). A filter, never a ranking.
`limit`	No	Max results (1-50).
`query`	Yes	Free-text search over name, description, and tags.
`trust`	No	verified = the resource's URN authority matches its catalog host (domain-anchored).
`domain`	No	Restrict to one publisher domain (e.g. stealthstack.ai).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes
`query`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / paid

Added value: +{
+  "description": "Only services that list this payment protocol (x402: pay-per-request in stablecoins). A filter, never a ranking.",
+  "enum": [
+    "x402"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / payment

Added value: +{
+  "description": "Payment terms the service lists (x402): protocol, lowest listed price + currency, network (CAIP-2). Self-declared; never a payee address.",
+  "properties": {
+    "currency": {
+      "type": "string"
+    },
+    "network": {
+      "type": "string"
+    },
+    "price": {
+      "type": "string"
+    },
+    "protocol": {
+      "type": "string"
+    },
+    "testnet": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "protocol"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely useful behavior: results are ranked by the index's relevance score with best match first, and each result carries a connect URL or inline connection/pull details. It does not mention rate limits, auth, or pagination beyond the limit parameter.

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?

Three sentences, front-loaded with the core search action and scope, then ranking, then result shape. It is efficient overall, though '(best match first)' is mildly redundant with 'ranked by the index's relevance score'.

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 an output schema present, return-value detail is not required, and the description still sketches the useful part (connect URL vs. inline details). Six parameters are fully covered by the schema, required query is stated, and the search/filter/rank model is complete for correct invocation.

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%, so the schema already documents all six parameters with their enums and the limit default. The description's filter list and the 'paid=x402' note largely restate the schema rather than adding new meaning beyond it, so the baseline of 3 applies.

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 names a specific verb and resource ('Search the StealthStack ARD index for agentic resources') and enumerates what is searched (agents, MCP servers, skills, catalogs). The free-text-over-name/description/tags mechanism and relevance ranking clearly separate it from the get_resource and list_resources siblings.

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 states the search context and which optional filters exist (kind, domain, trust, payment protocol), plus the clarifying note that paid=x402 'A filter, never a ranking.' However, it never names get_resource or list_resources or states when to prefer them over a query, so the routing guidance is context-only rather than explicit.

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

All StealthStack ARD Discovery tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?