AnyAPI

Check a request

get_request

Read-only

Inspect or resume a durable AnyAPI request returned by run_api. This reads AnyAPI's stored state and never repeats the paid provider dispatch. Poll again after retryAfterSeconds while status is queued or running.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	Yes	Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
`request_id`	Yes	durable request identifier returned by run_api

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No	optional nudge. 'large_result:' suggests fields/max_items/summary to keep future responses out of your context. 'paging_unavailable:' means this result came from a source that cannot return a nextCursor, so it may be INCOMPLETE and you cannot page further - re-run with requireFields ["nextCursor"] (may cost more per request) if you need the full list
`error`	No	safe AnyAPI failure code when durable work failed
`items`	Yes	number of result rows returned. For per-result SKUs the per-item cost is charged against this; for input-priced SKUs (perItemUnit != result) the charge is per submitted input, independent of this count
`output`	Yes	normalized output payload
`source`	No	the source that served this run: pass its id back in 'source' to prefer it again, or in 'ignoreSources' to avoid it. Absent when no source identity applies
`status`	No	durable request status: queued, running, succeeded, failed, or expired
`costUsd`	Yes	amount charged to the wallet in USD
`jqError`	No	present only when a jq expression failed; output then holds the full unshaped result and this explains why the reshape did not apply
`provider`	Yes	the provider serving the request (AnyAPI)
`replayed`	Yes	true when this response replays an identical earlier call (same API, same input) from the last few minutes instead of running again: nothing new was executed and costUsd restates the original charge, it was NOT charged a second time
`resultId`	No	opaque handle to the full result, cached ~15 min; pass it to read_result to dig deeper for free (no re-run, no charge). Absent when the result was too large to cache
`requestId`	No	durable request identifier; pass it to get_request to resume without repeating the paid POST
`nextAction`	No	machine-actionable resume instruction present while durable work is pending
`serviceOutcome`	No	end-to-end AnyAPI service outcome when known
`settlementState`	No	payment settlement state when known; independent of durable request status

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

addedOutput schema / properties / source

Added value: +{
+  "additionalProperties": false,
+  "description": "the source that served this run: pass its id back in 'source' to prefer it again, or in 'ignoreSources' to avoid it. Absent when no source identity applies",
+  "properties": {
+    "artworkKey": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "kind",
+    "artworkKey"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

Changed1 schema field changedSep 13, 2026

changedOutput schema / properties / hint / description

Previous value: -"optional nudge. 'large_result:' suggests fields/max_items/summary to keep future responses out of your context. 'paging_unavailable:' means this result came from a source that cannot return a nextCursor, so it may be INCOMPLETE and you cannot page further - re-run with requireCursor true (may cost more per request) if you need the full list"New value: +"optional nudge. 'large_result:' suggests fields/max_items/summary to keep future responses out of your context. 'paging_unavailable:' means this result came from a source that cannot return a nextCursor, so it may be INCOMPLETE and you cannot page further - re-run with requireFields [\"nextCursor\"] (may cost more per request) if you need the full list"

AddedSep 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context: reading persistent state, guaranteeing no repeat of the paid dispatch, and describing polling behavior. This goes beyond what the annotations alone communicate and does not contradict them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly written sentences, each earning its place: the operation, the safety/non-repeat guarantee, and the polling cadence. No filler, and the most important distinction is front-loaded.

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?

Given the output schema, annotations, and simple two-parameter interface, the description adequately covers purpose, non-repeat behavior, and when to poll again. It does not describe the final-result path or explicitly contrast with read_result, but that is not essential for a status-inspection tool.

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%, so the schema already fully documents request_id and context. The description references retryAfterSeconds and the origin of request_id, but adds no material parameter-level meaning beyond the schema's own descriptions.

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?

The description names a specific action ('Inspect or resume') on a specific resource ('a durable AnyAPI request returned by run_api') and immediately clarifies that it reads stored state. This clearly separates it from run_api, which creates the request, and gives the agent a precise mental model of what the tool does.

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?

The description gives explicit polling guidance: 'Poll again after retryAfterSeconds while status is queued or running.' It also implies the correct alternative avoidance by stating it 'never repeats the paid provider dispatch,' but it does not explicitly name alternatives such as read_result or run_api.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AnyAPI 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.