DropEngine x402 Agent Services

mcp_server_inspect

MCP server health check ($0.01 USDC on Base): connect to any public MCP endpoint over HTTPS, confirm it is reachable, list its tool names and input-schema summaries, compare against expected tool names, and flag risky or misleading tool descriptions. Read-only: inspected tools are never called. Use it before wiring an unknown MCP server into an agent, or to verify your own deployment. Pair with check_url to pre-screen a suspicious endpoint.

Agent entry points: risky external action → use Agent Action Gate when a combined action-specific safety assessment is needed; unclear capability/provider → use free /api/discover; constrained comparison between callable alternatives → use paid route_tool; known single capability → call the direct tool; multi-step objective → read the matching workflow recipe and call only relevant steps. Workflows are stateless recipes, not executors; calls are paid separately and are not bundle charged. Agent Action Gate does not approve payment, sign or broadcast transactions, evaluate seller reputation, replace transaction simulation, replace route_tool, or replace human approval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`endpoint`	Yes
`expected_tools`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`next`	No
`error`	No
`tools`	Yes
`result`	No
`server`	Yes
`status`	No
`payment`	No
`agent_ux`	No
`tool_count`	Yes
`capabilities`	Yes
`inspected_at`	Yes
`endpoint_host`	Yes
`expected_tools`	Yes
`tool_list_truncated`	Yes
`duplicate_tool_names`	Yes
`read_only_inspection`	Yes
`metadata_is_untrusted`	Yes
`tools_were_not_called`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 8, 2026

addedOutput schema / properties / agent_ux

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "meta": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "next": {
+      "items": {},
+      "type": "array"
+    },
+    "payment": {
+      "additionalProperties": false,
+      "properties": {
+        "execution_status": {
+          "enum": [
+            "not_started",
+            "succeeded",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "not_required",
+            "required",
+            "settled",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "execution_status"
+      ],
+      "type": "object"
+    },
+    "result": {},
+    "status": {
+      "enum": [
+        "succeeded",
+        "failed",
+        "partial",
+        "outcome_unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "result",
+    "error",
+    "meta",
+    "payment",
+    "next"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / meta

Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedOutput schema / properties / next

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedOutput schema / properties / payment

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "execution_status": {
+      "enum": [
+        "not_started",
+        "succeeded",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "not_required",
+        "required",
+        "settled",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "execution_status"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result
```
Added value: +{}
```
removedOutput schema / properties / status / const
```
Removed value: -"reachable"
```

addedOutput schema / properties / status / enum

Added value: +[
+  "succeeded",
+  "failed",
+  "partial",
+  "outcome_unknown"
+]

changedOutput schema / required

Previous value: -[
-  "status",
-  "endpoint_host",
-  "inspected_at",
-  "server",
-  "capabilities",
-  "tool_count",
-  "tool_list_truncated",
-  "duplicate_tool_names",
-  "expected_tools",
-  "tools",
-  "read_only_inspection",
-  "tools_were_not_called",
-  "metadata_is_untrusted"
-]New value: +[
+  "endpoint_host",
+  "inspected_at",
+  "server",
+  "capabilities",
+  "tool_count",
+  "tool_list_truncated",
+  "duplicate_tool_names",
+  "expected_tools",
+  "tools",
+  "read_only_inspection",
+  "tools_were_not_called",
+  "metadata_is_untrusted"
+]

First observedSep 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses read-only behavior ('inspected tools are never called'), the cost and payment rail ($0.01 USDC on Base), and that inspected content is only summarized, never executed. It does not cover failure modes (unreachable endpoint, invalid URL) or rate limits, so it falls short of full disclosure.

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

Conciseness3/5

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

The first paragraph is tight, front-loaded, and entirely on-point. The second 'Agent entry points' paragraph is long generic boilerplate that spends most of its words on other tools (Agent Action Gate, route_tool, /api/discover) and on what a sibling does not do, diluting the tool's own definition.

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?

An output schema exists, so return values need not be described. The description covers cost, read-only guarantee, and the full operation set, which is sufficient for a two-parameter inspection tool. Minor gaps remain around unreachable-endpoint handling and what happens when expected_tools is omitted.

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 description coverage is 0%, so the description must compensate. It implicitly maps both parameters: 'endpoint' via 'connect to any public MCP endpoint over HTTPS' (establishing the HTTPS requirement and public reachability) and 'expected_tools' via 'compare against expected tool names'. It adds meaning but no syntax, array limits, or format guidance beyond what the parameter names imply.

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 opens with a specific verb+resource ('MCP server health check') and enumerates the concrete operations: connect over HTTPS, confirm reachability, list tool names and input-schema summaries, compare against expected names, and flag risky descriptions. This is clearly distinguishable from siblings like check_url, scan_content, or route_tool.

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?

It states explicit when-to-use conditions ('before wiring an unknown MCP server into an agent, or to verify your own deployment') and names a complementary sibling ('Pair with check_url to pre-screen a suspicious endpoint'). The agent entry-points paragraph further routes between alternatives by scenario.

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

All DropEngine x402 Agent Services 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?