SqueezeOS — Institutional AI Market Intelligence

Recommend Capability

recommend_capability

Read-onlyIdempotent

Return the best-matching SqueezeOS capabilities for a natural-language need. Call this when an agent knows the goal, for example 'convert a URL to Markdown', but not which SML API serves it. Returns ranked capabilities with live endpoint and x402 payment metadata plus suggested next actions. Read-only and idempotent; no side effects. On error, returns a structured error. For example, ask 'which API verifies a fact' to get the fact-verification endpoint and its price.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max recommendations to return, 1-20. Default 5.
`query`	Yes	Natural-language description of what the agent needs, 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 / limit / description

Added value: +"Max recommendations to return, 1-20. Default 5."

addedInput schema / properties / query / description

Added value: +"Natural-language description of what the agent needs, 1-500 characters."

AddedAug 30, 2026

TDQS

A3.9/5.0

Behavior4/5

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

'Read-only and idempotent; no side effects' merely restates the annotations and earns no credit. The added value is genuine though: it discloses the return contents (ranked capabilities with live endpoint and x402 payment metadata plus suggested next actions) and error behavior ('returns a structured error'), which annotations do not cover.

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 the purpose, then use condition, then return/error behavior; the two examples aid selection. The sentence 'Read-only and idempotent; no side effects' is redundant against the annotations and does not earn its place.

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?

With an output schema present and rich annotations, the description does not need to explain result shapes in full, and it correctly focuses on selection guidance plus runtime metadata. It is complete enough for a 2-parameter read-only recommender, missing only sibling disambiguation.

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% and both parameters are fully documented in-schema (query length bounds, limit range and default), so the baseline is 3. The description adds no syntax or semantics beyond what the schema already states.

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 gives a specific verb and resource ('Return the best-matching SqueezeOS capabilities') plus a clear scenario (agent knows the goal but not which SML API serves it). It does not explicitly name siblings like discover_capabilities or compare_capabilities, so the agent must infer the boundary rather than being told it.

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?

'Call this when an agent knows the goal ... but not which SML API serves it' is a clear use condition, reinforced by two concrete examples. No explicit when-not or named alternative is provided, so routing against sibling discovery tools is left partly to inference.

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.