Ahel

Read a run's status and results

capability_run_status

Read-onlyIdempotent

Without execution_id: the paid data capabilities this workspace can run, each with its providers and exact prices. With execution_id: that run's state, attempts and exact cost, settled once in the ledger when final; with results true, its rows and provenance (include_raw true adds the provider's own answer), and, when it has rows, results_page and csv_url: give the person those links instead of writing the rows out again. Generated images and audio come as a signed link (media_url, valid for days) with their type and size; a small one is also attached as an image or audio block. A long result answers as many rows as fit and says the offset that reads the rest. NOT for: finding a task or tool to run, which is capability_search.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "capability_run_status"
  }
}

Input Schema

Name	Required	Description
`offset`	No	With results: the first row to answer (0-based), from next_offset when a long result did not fit in one answer. Default 0.
`results`	No	With execution_id: include the rows.
`full_text`	No	With results: answer long text values whole. By default a result of several rows cuts each text value at 4000 characters and lists the cut fields in that row's truncated_fields.
`max_items`	No	With results: the max_items the run was started with, so the answer can say when the rows stopped at that limit. run_capability's next names it.
`include_raw`	No	With results: also include the winning provider's own answer (raw) and the normalised output. Large and repeats the rows; leave it out unless the rows lack a field you need.
`execution_id`	No	The id run_capability answered.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / max_items

Added value: +{
+  "description": "With results: the max_items the run was started with, so the answer can say when the rows stopped at that limit. run_capability's next names it.",
+  "type": "number"
+}

First observedNov 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds substantial context on top: cost is settled once in the ledger when final, media arrives as a signed link valid for days with an inline block for small files, long results truncate at 4000 characters with truncated_fields, and include_raw is flagged as large and redundant. That is exactly the kind of behavior the structured fields cannot convey.

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 most important distinction, the two operating modes, is front-loaded in the first two clauses, and every sentence carries operational information. It is, however, packed into long semicolon-chained sentences that are harder to scan than they need to be for a six-clause contract.

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?

There is no output schema, so the description carries the full return-shape burden and does so: state, attempts, exact cost, rows with provenance, raw provider answer, media_url with type and size, results_page, csv_url, next_offset and truncated_fields are all named. Nothing an agent needs in order to call or report results correctly is missing.

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%, so the six parameters are already documented in the input schema, and much of the description's parameter talk (offset from next_offset, max_items from run_capability's next, include_raw's size warning) restates that text. The description does add value by explaining how results, include_raw and full_text interact in a single call, but this is a 3 baseline case where the schema does the heavy lifting.

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 splits the tool into two explicitly scoped modes: without execution_id it returns the paid capabilities a workspace can run with providers and prices; with execution_id it returns that run's state, attempts, cost and optionally rows. It names the sibling it is not (capability_search) so an agent can route without opening either schema.

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?

Usage is stated for both modes plus a clear exclusion: 'NOT for: finding a task or tool to run, which is capability_search.' It also instructs the agent to hand back results_page/csv_url links rather than re-writing rows. The remaining gap is the boundary against capability_inspect, since the no-execution_id mode also lists capabilities and the description does not say when to prefer that sibling.

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

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