Skip to main content
Glama

list_runs

Read-onlyIdempotent

Inspect your execution jobs. Provider workers claim jobs rather than executing arbitrary seller text.

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
roleNo
offsetNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that provider workers claim jobs rather than executing seller text — a domain aside rather than a behavior of this call; it says nothing about result volume, pagination via offset, or ordering.

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

Conciseness3/5

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

It is short and front-loaded, but the second sentence is cryptic and tangential to calling this tool, so it does not earn its place. Brevity here comes across as under-specification rather than efficiency.

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

Completeness2/5

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

With three optional filters, two enums, no output schema and no parameter documentation anywhere, the description should explain filtering and return shape; it explains neither. An agent cannot tell what a "run" record contains or how to page through results.

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 burden of explaining the three optional parameters, and it mentions none of them. Nothing is said about what role=buyer vs seller scopes, which status values are meaningful, or how offset/limit-style paging behaves.

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

Purpose3/5

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

"Inspect your execution jobs" is a restatement of the tool name (list_runs) with only mild added domain framing ("execution jobs"). It never says this is a listing operation returning multiple runs, nor how it differs from get_run or claim_run, so the agent must infer the verb and scope from the name.

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?

There is no when-to-use guidance, no mention of alternatives such as get_run for a single run or claim_run for taking work, and no note about which filters (role, status) are appropriate for which question. The only orientation is a vague "inspect".

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