StealthStack ARD Discovery

Browse discovered agentic resources

list_resources

Read-onlyIdempotent

Browse the StealthStack ARD index — agentic resources (agents, MCP servers, skills, catalogs) discovered across the open web. Optionally filter by kind, domain, trust, or accepted payment protocol (paid=x402). Returns a count, a kind breakdown, and the page of resources, each with its connect URL when the publisher provides one; otherwise the inline connection or pull details. Use search_resources for a specific need.

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).
`trust`	No	Restrict by trust status.
`domain`	No	Restrict to one publisher domain (e.g. stealthstack.ai).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`byKind`	No
`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.3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful behavioral detail (returns a count, kind breakdown, page of resources, connect URL or inline connection/pull details) and clarifies that paid is 'a filter, never a ranking' — a genuine non-obvious trait. But return content is largely restated and an output schema exists, so this is solid rather than exceptional.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool browses before the filter list, and the routing hint comes last where it belongs. No sentence is wasted.

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?

Annotations carry the safety profile and an output schema exists, so the description need not document return shapes exhaustively — yet it still sketches them. For a zero-required-parameter browse tool, 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented with its enum values and defaults; the baseline is 3. The description lists the same filters (kind, domain, trust, payment protocol) and adds only the parenthetical 'paid=x402', which is a marginal gain over the schema's own enum description.

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 (Browse) plus the resource (the StealthStack ARD index of agentic resources) and enumerates what lives there: agents, MCP servers, skills, catalogs. It is clearly distinguishable from get_resource (single item) and search_resources (targeted lookup) without opening any 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?

Explicitly routes the agent to the alternative: 'Use search_resources for a specific need,' implying this tool is for broad browsing. The conditional selection rule between browsing and searching is stated outright rather than inferred.

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?