SqueezeOS — Institutional AI Market Intelligence

Aftersearch Resolve

aftersearch_resolve

Convert a natural-language query into machine intent, a bounded Evidence Pack, and one immutable x402 job with a fresh quote pointer. Use this when an agent needs to turn a what-would-I-Google question into a priced, quotable evidence job before any payment. Returns the immutable job_id plus the public job summary; on invalid input returns a structured input_rejected error instead of a job. Creates one server-side job record per call (a side effect) but never spends or moves funds. For example, asking whether a token contract is safe becomes an intent-scored Evidence Pack with fresh PAYMENT-REQUIRED terms.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	The natural-language question to compile into intent and an Evidence Pack (1-60000 chars).

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.

Changed2 schema fields changedOct 14, 2026

changedInput schema / properties / query / description

Previous value: -"The natural-language question to compile into intent and an Evidence Pack (1-8000 chars)."New value: +"The natural-language question to compile into intent and an Evidence Pack (1-60000 chars)."

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

Added value: +"The natural-language question to compile into intent and an Evidence Pack (1-8000 chars)."

AddedSep 18, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that each call creates one server-side job record (a side effect, consistent with readOnlyHint=false and idempotentHint=false), guarantees no funds are spent or moved, and specifies the failure mode (structured input_rejected instead of a job). This is exactly the extra context 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?

Front-loaded with the core transformation, then behavior and error semantics in descending priority. Slightly redundant between the opening purpose sentence and the 'Use this when...' sentence, but no padding overall.

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 it wisely avoids detailing return fields, yet still covers what an agent needs that the schema does not: the per-call job-record side effect, the no-funds guarantee, immutability of the job, and the input_rejected error path. Nothing material is missing for a pre-payment compile step.

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% for the single parameter, so the schema already defines the query and its length bounds. The description only restates it as a natural-language question, adding no new syntax, format, or constraint detail; baseline 3 applies.

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 concrete transformation: natural-language query -> machine intent + Evidence Pack + one immutable x402 job with a fresh quote pointer. The 'before any payment' framing and the example ('whether a token contract is safe') let an agent distinguish this from the quote/accept siblings.

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?

Explicitly names the condition for use ('when an agent needs to turn a what-would-I-Google question into a priced, quotable evidence job before any payment'), which positions it ahead of the settlement-oriented siblings. It stops short of naming the alternatives (aftersearch_quote, aftersearch_accept) or stating when NOT to use it.

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.