SqueezeOS — Institutional AI Market Intelligence

Inspect Capability

inspect_capability

Read-onlyIdempotent

Inspect one live SqueezeOS capability by its sml_id. Use this when an agent has a candidate capability and needs its exact endpoint, parameters, and x402 payment terms before calling. Returns real endpoint and payment metadata plus, when safe, a real liveness probe rather than an invented reliability score. Read-only and idempotent; no side effects. On error, returns a structured error. For example, inspect 'url-to-markdown' to confirm its price and required payment-signature header.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`probe`	No	When true, performs a real liveness probe of the capability. Default true.
`sml_id`	Yes	The capability's sml_id from discovery, 1-500 characters.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	Whether the upstream HTTP status is 2xx; not settlement proof.
`body`	No	Unmodified upstream JSON, or bounded response text. Consult that capability's live schema.
`error`	No
`charged`	No	Present on local/transport failures; these do not establish an upstream charge.
`message`	No
`auto_spent`	No
`status_code`	No	Observed upstream HTTP status, or null when no response was obtained.
`substituted`	No
`content_type`	No
`payment_required`	No	Observed PAYMENT-REQUIRED header; a challenge does not prove payment.
`payment_response`	No	Observed PAYMENT-RESPONSE header. Assess it together with accepted delivery.
`caller_supplied_authorization`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "ok",
+        "status_code"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Canonical REST response envelope, or a local/transport rejection. Upstream data remains in body and is defined by the live capability schema.",
+  "properties": {
+    "auto_spent": {
+      "const": false
+    },
+    "body": {
+      "description": "Unmodified upstream JSON, or bounded response text. Consult that capability's live schema."
+    },
+    "caller_supplied_authorization": {
+      "type": "boolean"
+    },
+    "charged": {
+      "const": false,
+      "description": "Present on local/transport failures; these do not establish an upstream charge."
+    },
+    "content_type": {
+      "type": "string"
+    },
+    "error": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the upstream HTTP status is 2xx; not settlement proof.",
+      "type": "boolean"
+    },
+    "payment_required": {
+      "description": "Observed PAYMENT-REQUIRED header; a challenge does not prove payment.",
+      "type": "string"
+    },
+    "payment_response": {
+      "description": "Observed PAYMENT-RESPONSE header. Assess it together with accepted delivery.",
+      "type": "string"
+    },
+    "status_code": {
+      "description": "Observed upstream HTTP status, or null when no response was obtained.",
+      "maximum": 599,
+      "minimum": 100,
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "substituted": {
+      "const": false
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / probe / description

Added value: +"When true, performs a real liveness probe of the capability. Default true."

addedInput schema / properties / sml_id / description

Added value: +"The capability's sml_id from discovery, 1-500 characters."

Changed6 schema fields changedAug 30, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / probe / default
```
Added value: +true
```
- removedInput schema / properties / probe / description
```
Removed value: -"Attempt a real liveness probe when safe to do so (default true)"
```
- removedInput schema / properties / sml_id / description
```
Removed value: -"The sml_id from a mesh_discover result"
```
- addedInput schema / properties / sml_id / maxLength
```
Added value: +500
```
- addedInput schema / properties / sml_id / minLength
```
Added value: +1
```
AddedAug 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the restated 'Read-only and idempotent; no side effects' sentence earns little. Beyond that, the description adds real behavioral context: the probe is a genuine liveness check rather than a fabricated reliability score, and errors return a structured error object.

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?

Purpose and usage condition are front-loaded in the first two sentences, and the concrete example at the end is genuinely useful. It is slightly padded: the read-only/idempotent sentence duplicates annotations, and 'On error, returns a structured error' is close to a tautology.

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-value documentation is unnecessary, and the description covers purpose, precondition, behavior, and error handling. The only meaningful gap is not routing the agent to a sibling when the capability is not yet identified.

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 both sml_id and the probe boolean with its default. The description mentions the liveness probe but adds no syntax, format, or cost guidance beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Inspect one live SqueezeOS capability by its sml_id') and scopes it to a single capability rather than a set. It implies differentiation from the discovery/compare siblings ('when an agent has a candidate capability'), but never names an alternative tool, so it stops short of full sibling separation.

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 gives a clear triggering condition: use it when a candidate capability is already in hand and its endpoint, parameters, and x402 payment terms are needed before calling. It does not, however, name the nearest alternative (e.g. read_capability or x402_contract) or state when this tool is the wrong choice.

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

All SqueezeOS — Institutional AI Market Intelligence 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.