SqueezeOS — Institutional AI Market Intelligence

Execute Capability

execute_capability

Destructive

Execute one public SqueezeOS REST path with POST after confirm_write=true. Returns the target result or its x402 challenge. A caller-signed payment_signature may authorize the published SML service fee; the server does not sign wallets. May create records or settle an authorized fee. Operator routes and off-host URLs are denied. API schemas: https://squeezeos-api.onrender.com/.well-known/openapi.json.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "confirm_write": "<confirm_write>"
    },
    "name": "execute_capability"
  }
}

Input Schema

Name	Required	Description
`body`	No	Optional request body for POST: object, array, string, number, boolean, or null.
`path`	Yes	Concrete SqueezeOS path beginning with /; do not pass a full URL.
`query`	No	Optional object of URL query parameters.
`confirm_write`	Yes	Explicitly authorize this POST operation.
`payment_signature`	No	Canonical x402 v2 PAYMENT-SIGNATURE value bound to this exact target-resource challenge.
`alternative_intent`	No	Optional natural-language intent used to rank the closest SML alternative after an unsigned HTTP 402.

Output 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.

AddedOct 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already flag destructive/openWorld/non-idempotent, and the description adds genuinely new context beyond them: that execution may create records or settle an authorized fee, that the server never signs wallets, that off-host and operator routes are denied, and that an unsigned call returns an x402 challenge. This is exactly the behavioral detail annotations cannot carry.

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?

The write-gate and return behavior are front-loaded, and each sentence carries information (denials, payment, API schema link). It is dense with domain jargon (SML, x402, SqueezeOS) that slightly taxes first-read parsing, but there is no redundant filler.

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, the description need not detail return values, yet it still sketches the two outcomes (target result or x402 challenge). Combined with auth/fee handling, denial rules, and a link to the API schema, an agent has everything needed to invoke it safely.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: confirm_write is a write authorization gate, payment_signature is caller-signed and authorizes the published SML service fee (server does not sign), and the path must be a concrete public path rather than a full URL. It goes beyond restating the schema fields.

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 states a concrete verb and resource — 'Execute one public SqueezeOS REST path with POST' — and constrains scope to public paths while denying operator routes and off-host URLs. It is clear what the tool does, though it never names the sibling it competes with (e.g. call_capability / read_capability), so differentiation is inferred from scope rather than stated.

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 hard prerequisite ('after confirm_write=true'), notes that a caller-signed payment_signature may be needed to settle the published fee, and discloses that operator routes and off-host URLs are rejected. No explicit alternative tool is named for when this is the wrong choice, so it falls short of full when/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.