Skip to main content
Glama

List StewAI Runs

list_runs
Read-onlyIdempotent

List recent runs owned by the authenticated account, with optional recipe and status filters.

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": "list_runs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
statusNo
recipe_refNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the ownership scoping (only the authenticated account's runs are returned), but says nothing about ordering, pagination behavior, or the effective result cap beyond what the schema enforces.

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?

A single front-loaded sentence with no filler. It is efficient, though it is perhaps too spare given the undocumented pagination parameters that a slightly longer sentence could have addressed.

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?

The tool is a simple filtered list with an output schema, so return values need no explanation and annotations cover the safety profile. The remaining gap is pagination semantics (limit cap of 20, cursor usage), which the agent must infer from the schema alone.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it only covers two of the four parameters: the recipe filter and the status filter. The limit and cursor parameters — the entire pagination mechanism — get no explanation of meaning or expected values.

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

Purpose4/5

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

The description names a specific verb and resource ("List recent runs") and scopes it to "owned by the authenticated account," which is more precise than the title alone. It does not explicitly distinguish itself from sibling listing tools such as list_run_steps, but the resource is unambiguous.

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

Usage Guidelines3/5

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

Mentioning "optional recipe and status filters" implies the intended use case (browse recent runs, narrow by recipe or status), but there is no explicit when-to-use guidance, no note about paging through results, and no pointer to a sibling for per-run detail.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources