Skip to main content
Glama

run_list

List runs, newest first. Paged like document_list: {data, has_more, next_cursor}.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
statusNo
document_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the sort order and the exact response envelope ({data, has_more, next_cursor}), which is genuinely useful behavioral context. It omits permission requirements, whether the operation is strictly read-only, and how filtering by status or document_id affects results.

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?

Two short sentences, front-loaded with the operation and ordering, with no filler. The second sentence packs pagination and return shape efficiently, though its brevity leaves the filter parameters unexplained.

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?

For a four-parameter listing tool with no annotations and no output schema, the description should explain the filter parameters and default/maximum page size behavior. It covers ordering and the response envelope but leaves half the contract, particularly status and document_id filtering, undefined.

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% across four parameters, and the description only gestures at pagination via the cursor/has_more/next_cursor mention. It never explains what limit bounds, what status values are accepted, or how document_id scopes the list, so the agent must guess at filter semantics.

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?

States a specific verb and resource ("List runs") and adds the ordering guarantee "newest first", so an agent knows the operation and sort order without opening a schema. It does not distinguish itself from sibling listing tools such as group_run_list or run_get, so it falls short of a 5.

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 exclusion of alternatives, and no statement of prerequisites. The reference to document_list explains pagination mechanics rather than when this tool should be chosen over group_run_list or run_get.

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