SqueezeOS — Institutional AI Market Intelligence

Agent Web Access

agent_web_access

Fetch LLM-ready Markdown from any public HTTPS URL through the SML Clean Web Reader. Use this when an agent needs a web page's content as compact Markdown, for example to ground a research answer, without a separate SML account or API key. Returns the converted Markdown up to max_chars. An unsigned call returns the live x402 PAYMENT-REQUIRED challenge and never auto-spends; retry only with a challenge-specific payment_signature. Unsigned calls are read-only and idempotent with no side effects; a supplied signature authorizes one paid, irreversible x402 settlement in USDC on Base. On error, returns a structured error. For example, fetch a documentation page before summarizing it.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Public HTTPS URL to read.
`max_chars`	No	Maximum Markdown characters to return, 1000-50000. Default 12000.
`payment_signature`	No	Canonical x402 v2 PAYMENT-SIGNATURE bound to this exact Agent Web Access challenge.

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"
+}

Changed1 schema field changedOct 5, 2026
- addedInput schema / properties / max_chars / description
```
Added value: +"Maximum Markdown characters to return, 1000-50000. Default 12000."
```
AddedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by spelling out the payment flow: an unsigned call returns the live x402 PAYMENT-REQUIRED challenge and never auto-spends, whereas supplying a challenge-specific signature authorizes exactly one paid, irreversible USDC settlement on Base. It also states that errors return a structured error, which the schema and annotations do not.

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 core capability and the unsigned-vs-signed split are front-loaded, and no sentence is filler. It is fairly dense and the payment mechanics arrive in a long middle block, but the length is justified by the security-sensitive behavior being described.

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?

For a three-parameter tool with a full output schema, the description covers everything an agent needs: what is fetched, the truncation bound, the two distinct call modes, the payment/authorization semantics, and error behavior. Return-format details are correctly left to the output schema.

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: it ties the return size explicitly to max_chars and constrains payment_signature to a 'challenge-specific' value that should only be retried after receiving the challenge. It does not clarify URL host/redirect handling beyond 'public HTTPS'.

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 (fetch), resource (LLM-ready Markdown from any public HTTPS URL) and the mechanism (SML Clean Web Reader). It is clearly distinguishable from the sibling tools, which cover capability discovery, x402 contract/evidence, and quoting rather than raw page conversion.

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 a concrete usage context (grounding a research answer, e.g. fetching a documentation page before summarizing) and the key precondition that no separate SML account or API key is needed. It does not name an alternative sibling tool to use instead in overlapping scenarios, so it falls just short of explicit 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.