StealthStack ARD Discovery

Get install and connect details

get_resource

Read-onlyIdempotent

Get install and connect details for one resource found with search_resources or list_resources, by its identifier. Call it after a search, before you install or connect anything. Returns the connect URL or install command (npm, PyPI or Docker package when one is listed), transport, repository, publisher, version, auth and payment terms when known, the publisher's description, tags and example queries.

Input Schema

Name	Required	Description	Default
`identifier`	Yes	The `id` of a search_resources or list_resources result, e.g. urn:air:stealthstack.ai:skill:parquet (urn:ai: and urn:air: prefixes are both accepted).

Output Schema

Name	Required	Description
`found`	Yes
`resource`	No
`resolvedIdentifier`	No	The identifier the index matched (may use the other URN prefix).
`requestedIdentifier`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026

changedInput schema / properties / identifier / description

Previous value: -"The resource URN, e.g. urn:air:stealthstack.ai:skill:parquet (urn:ai: and urn:air: are both accepted)."New value: +"The `id` of a search_resources or list_resources result, e.g. urn:air:stealthstack.ai:skill:parquet (urn:ai: and urn:air: prefixes are both accepted)."

addedOutput schema / properties / resource / properties / access

Added value: +{
+  "description": "What is known about auth and pricing. requiresAuth comes from the MCP Registry entry; auth and pricing are StealthStack's automated labels (unknown values omitted).",
+  "properties": {
+    "auth": {
+      "type": "string"
+    },
+    "pricing": {
+      "type": "string"
+    },
+    "requiresAuth": {
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / resource / properties / install

Added value: +{
+  "description": "Packages to install the server from (MCP Registry entries). `command` is a ready-to-run start command (npx / uvx / docker / cargo), present only when the package name passes a strict charset check.",
+  "items": {
+    "properties": {
+      "command": {
+        "type": "string"
+      },
+      "env": {
+        "description": "Required environment variable names the package lists (names only).",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "package": {
+        "type": "string"
+      },
+      "registry": {
+        "type": "string"
+      },
+      "transport": {
+        "type": "string"
+      },
+      "version": {
+        "type": "string"
+      },
+      "versionRejected": {
+        "description": "The listed version failed validation; `command` is not pinned to it.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "registry",
+      "package"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / resource / properties / repository

Added value: +{
+  "description": "Source repository URL (https), as listed.",
+  "type": "string"
+}

Changed1 schema field changedOct 7, 2026

addedOutput schema / properties / resource / 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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the bar is lower. The description adds real context: the payload contents (connect URL or npm/PyPI/Docker install command, transport, repository, publisher, version, auth and payment terms, tags, example queries) and the 'when known' caveat that fields may be absent. It doesn't mention pagination or error behavior, which keeps it off a 5.

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 purpose and ordering before the payload enumeration. The long comma-separated list of returned fields is informative but dense; a slight trim would improve scannability without losing meaning.

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?

One fully documented parameter, an output schema present, and rich annotations — the description covers everything an agent needs to decide to call it and to interpret the result. Nothing material 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 coverage is 100%, and the schema itself documents the URN format and accepted prefixes, so the schema does the heavy lifting. The description only adds provenance ('found with search_resources or list_resources'), which is a mild but useful addition — baseline 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?

States a specific verb and resource ('Get install and connect details for one resource') and explicitly scopes it to records produced by search_resources or list_resources, which separates it cleanly from those siblings. An agent can tell what it returns without opening the 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?

Gives explicit sequencing: 'Call it after a search, before you install or connect anything.' It names the sibling tools that supply the identifier, so the agent knows which tool to use first and which one this complements.

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

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.

Resources

Need Help?