AlphaWeb

agent_runs_list

Read-only

Read hosted run usage and untrusted summaries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "agent_runs_list"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No
`agent`	No
`limit`	No
`since`	No
`cursor`	No
`status`	No
`trigger`	No
`workspace`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

D1.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The phrase 'untrusted summaries' adds a vague security caveat, but the description does not explain pagination, limits, filters, or what the returned run summaries contain.

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

Conciseness2/5

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

It is a single short sentence, but it is under-specified rather than effectively concise. For an 8-parameter listing tool, the description is too thin to be structurally useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the eight query parameters, lack of an output schema, and the existence of closely related sibling tools, the description is far too sparse. It does not explain filters, pagination, or how to interpret the returned summaries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 8 parameters with 0% description coverage, and the description does not mention any of them. Filters such as kind, agent, since, status, trigger, limit, and cursor are completely undocumented beyond their bare schema types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Read hosted run usage and untrusted summaries,' which gestures at reading agent run data but never clearly states that this is a list/history operation. It does not distinguish the tool from siblings like agent_runs_get or agent_runs_start.

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

Usage Guidelines2/5

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

It gives no indication of when to use this tool versus agent_runs_get, agent_runs_start, or agent_runs_cancel. The usage context is only implied by the tool name, not by the description.

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

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

Resources

Need Help?