Skip to main content
Glama
Sign In

neonloops

by com.neonloops
OverviewDiscussionsAdmin

Runs: list

runs_list
Read-only

Lists what this neonloops workspace's workflows have run, newest first, 20 to a page: status, trigger, timing, price and the End step's summary. Narrow it to one workflow or to some statuses, and page with nextCursor. Use it to see whether a workflow ran, when, and how it ended; runs_get then opens one run. A run's Start inputs come as a byte size and a 200-character preview, a null field is left out of its row, and priceUsd is the run's stored price (null while pending; pricePartial is true while the run is still going). A value a Start marks sensitive reads "Hidden from viewers" unless the token may read documents. For a workflow's definition use workflows_get.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRuns per page: default 20, max 100.
cursorNoThe previous page's nextCursor, a timestamp, to read the next older page. Omit for the first page.
statusNoOnly runs in these statuses (queued, running, succeeded, failed or cancelled). Omit for every status.
workflow_idNoOnly this workflow's runs, by id as workflows_list gives it. Omit for the whole workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"The previous page's `nextCursor`."New value: +"The previous page's nextCursor, a timestamp, to read the next older page. Omit for the first page."
    • changedInput schema / properties / limit / description
      Previous value: -"Default 20, max 100."New value: +"Runs per page: default 20, max 100."
    • changedInput schema / properties / status / description
      Previous value: -"Narrow to these statuses only."New value: +"Only runs in these statuses (queued, running, succeeded, failed or cancelled). Omit for every status."
    • changedInput schema / properties / workflow_id / description
      Previous value: -"Narrow to one workflow. Omit for the whole workspace."New value: +"Only this workflow's runs, by id as workflows_list gives it. Omit for the whole workspace."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the read-only/non-destructive safety profile; the description goes well past that, disclosing newest-first ordering, 20-per-page default, null fields being omitted from rows, priceUsd/pricePartial semantics while a run is pending, Start inputs truncated to a byte size and 200-character preview, and that sensitive values read 'Hidden from viewers' unless the token may read documents. That is substantial operational context an agent would otherwise have to discover by trial.

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?

Front-loaded with the core action and scoping, then layering return-value detail; each sentence carries information. It is dense but slightly overpacked — the Start-input/price clause is a long compressed run-on that would read better split — so not a 5.

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 must explain returns, and it does: the row fields (status, trigger, timing, price, End step's summary), pagination via nextCursor, price nullability, and redaction rules. For a four-parameter, zero-required list tool this leaves nothing an agent needs before calling it.

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 all four parameters (limit, cursor, status, workflow_id) are already documented, and the description mostly restates them ('page with nextCursor', 'narrow it to one workflow or to some statuses'). It adds only mild reinforcement — newest-first implies cursor direction — so the baseline of 3 applies.

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?

States a specific verb and resource ('Lists what this neonloops workspace's workflows have run'), plus the ordering and default page size. It also names the two nearest siblings — runs_get for a single run and workflows_get for the definition — so an agent can disambiguate without opening any schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it ('to see whether a workflow ran, when, and how it ended') and routes to alternatives for adjacent needs: runs_get then opens one run, workflows_get for the definition. Narrowing behavior is also spelled out ('Narrow it to one workflow or to some statuses').

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

All neonloops toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources