SqueezeOS — Institutional AI Market Intelligence

Aftersearch Quote

aftersearch_quote

Read-onlyIdempotent

Return fresh x402 PAYMENT-REQUIRED terms for one immutable job. Call this when an agent holds a job_id and needs the current USDC price and payment instructions before deciding to pay; a 402 challenge is a quote, never payment. Returns the price in USDC, the pay_to address, network, and asset for that exact job; on an unknown job_id returns a structured job_not_found error. Read-only and idempotent; no side effects. For example, quoting a job_id returned by aftersearch_resolve yields its exact USDC terms for this job only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	The 24-char hex job_id returned by aftersearch_resolve or aftersearch_verify_serp.

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 / job_id / description

Added value: +"The 24-char hex job_id returned by aftersearch_resolve or aftersearch_verify_serp."

AddedSep 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, and the description partly restates that ('Read-only and idempotent; no side effects'). It goes beyond annotations by disclosing error behavior ('structured job_not_found error' on unknown job_id), the freshness/dynamic nature of the terms, and the quote-vs-payment semantic.

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 core purpose and the trigger condition, then return fields, error behavior, and an example. Mostly efficient, though 'Read-only and idempotent; no side effects' is redundant with the annotations and adds length without new information.

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?

A single required, fully specified parameter, complete annotations, and an output schema mean the definition need not explain return values. The description still covers purpose, trigger, error case, and semantics, leaving nothing an agent needs to call it correctly.

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 the single job_id is fully documented with pattern and source. The description reinforces the source of the id ('returned by aftersearch_resolve') and adds the 'exact job only' scoping, but adds little syntax or format detail beyond the schema, so the baseline of 3 holds.

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 (Return) and resource (fresh x402 PAYMENT-REQUIRED terms for one immutable job), including the exact fields returned (USDC price, pay_to, network, asset). It is clearly distinguishable from siblings like aftersearch_accept and aftersearch_resolve.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the precondition ('when an agent holds a job_id') and the decision context ('needs the current USDC price and payment instructions before deciding to pay'), and contrasts with the payment step by noting 'a 402 challenge is a quote, never payment'. The example ties it to aftersearch_resolve as the job_id source.

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.