Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

workflow_execution_list

Read-only

List workflow executions with optional filters and pagination.

Filters:

  • workflowId: Filter by logical workflow ID

  • status: Filter by execution status (PENDING, RUNNING, COMPLETED, FAILED)

  • startDateFrom/startDateTo: Filter by start time range (ISO 8601 format)

  • limit/offset: Pagination (default limit: 20, max: 100)

Returns execution summaries including status, timing, and token usage.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 20, max: 100)
offsetNoNumber of results to skip (default: 0)
statusNoFilter by execution status: PENDING, RUNNING, COMPLETED, FAILED
workflowIdNoFilter by workflow ID (logical workflow ID)
startDateToNoFilter executions started before this date (ISO 8601 format)
startDateFromNoFilter executions started after this date (ISO 8601 format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description still adds real value by stating what comes back ('execution summaries including status, timing, and token usage'), which matters because there is no output schema, and it restates the max:100 cap that bounds behavior.

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 lead sentence followed by a scannable bulleted filter list and a return-value line — appropriate for a six-parameter tool. The bullets duplicate schema text, which is mild waste, but the structure makes it fast to skim.

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?

For a read-only, non-destructive list tool with full schema coverage and no output schema, the description covers filters, pagination bounds, and the shape of returned summaries. Nothing an agent needs in order to call it correctly is missing, and a return schema is absent so return description is warranted.

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 description coverage is 100%, so every parameter is already documented, including ISO 8601 format for the date filters and the status enumerations. The description's filter list is essentially a mirror of the schema and contributes no format nuances, defaults, or interaction rules the schema lacks, so the baseline of 3 applies.

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 opens with a specific verb and resource ('List workflow executions') plus scope qualifiers ('optional filters and pagination'), which is unambiguous. It does not name the sibling workflow_execution_get_steps as the detail-oriented alternative, so an agent must infer the split from sibling names alone.

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?

Usage is only implied: it is a discovery/list tool versus workflow_execution_get_steps for step-level detail, but the description never says when to pick one over the other. There are no exclusions or prerequisites, though for a read-only filtered list the implied usage is fairly safe.

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

All Spaces by Peakflo toolsInspect
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