SqueezeOS — Institutional AI Market Intelligence

Compare Capabilities

compare_capabilities

Read-onlyIdempotent

Compare 2-5 live SqueezeOS capabilities side by side using real metadata. Use this when an agent must choose between similar APIs, for example weighing price against coverage. Returns the same real endpoint and payment fields inspect_capability returns for each candidate; no fabricated composite score is produced. Read-only and idempotent; no side effects. On error, returns a structured error. For example, compare two web-reader capabilities before routing a research task.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`probe`	No	When true, performs a real liveness probe of each capability. Default true.
`sml_ids`	Yes	Array of 2-5 sml_id values to compare.

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 each capability. Default true."

addedInput schema / properties / sml_ids / description

Added value: +"Array of 2-5 sml_id values to compare."

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 real liveness probes when safe to do so (default true)"
```
- removedInput schema / properties / sml_ids / description
```
Removed value: -"2-5 sml_ids from mesh_discover results to compare"
```
- addedInput schema / properties / sml_ids / items / maxLength
```
Added value: +500
```
- addedInput schema / properties / sml_ids / items / minLength
```
Added value: +1
```
AddedAug 20, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already cover readOnly/idempotent/destructive, but the description adds meaningful traits: metadata is real, no fabricated composite score, a real liveness probe, and structured errors. It also states what is returned is the same endpoint/payment fields as inspect_capability, which goes beyond the annotation set.

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?

Front-loaded with purpose and usage, and most sentences earn their place. 'Read-only and idempotent; no side effects' largely restates the annotations, which is the one mildly redundant sentence.

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 values need no elaboration, and the description still clarifies the shape of results (same fields as inspect_capability). Usage, error behavior, and safety are all covered for a 2-parameter read tool.

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 both parameters are documented in the schema (sml_ids 2-5, probe default true), so the schema carries the load. The description only implicitly gestures at the probe via 'live'/'real metadata' without explaining the boolean switch or its cost/latency implication.

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 (compare), resource (live SqueezeOS capabilities), and scope (2-5, side by side, real metadata). It distinguishes itself from the single-target sibling 'inspect_capability' by naming what it returns relative to that tool.

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?

Gives explicit context ('when an agent must choose between similar APIs, for example weighing price against coverage') plus a concrete scenario ('compare two web-reader capabilities before routing a research task'). It does not explicitly name when to use inspect_capability or recommend_capability instead, so it stops short of full when-not guidance.

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.