Skip to main content
Glama
geored

Lumino

list_pipelineruns

Retrieve Tekton PipelineRuns from a Kubernetes namespace to monitor execution status, timing, and completion details for pipeline analysis.

Instructions

List Tekton PipelineRuns in a namespace with status and timing details.

Args:
    namespace: Kubernetes namespace to query.

Returns:
    List[Dict]: PipelineRuns with keys: name, pipeline, status, started_at, completed_at, duration.
                Empty list if none found. [{"error": "msg"}] on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It discloses return format and error handling, but lacks details on permissions, rate limits, or side effects. It adequately describes output behavior but misses operational constraints.

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

Conciseness5/5

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

Front-loaded with purpose, followed by structured Args and Returns sections. Every sentence adds value: the first defines scope, the second explains the parameter, and the third details return format and error handling—no wasted words.

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?

Given no annotations, 0% schema coverage, but an output schema exists, the description is reasonably complete. It covers purpose, parameter meaning, and return values, though it could benefit from more behavioral context like authentication or limitations.

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

Parameters4/5

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

Schema coverage is 0%, but the description compensates by explaining the single parameter 'namespace' as 'Kubernetes namespace to query', adding clear meaning beyond the schema's title. For a tool with only one parameter, this provides sufficient semantic context.

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?

The description clearly states the specific action ('List Tekton PipelineRuns'), resource ('in a namespace'), and scope ('with status and timing details'). It distinguishes from siblings like 'get_tekton_pipeline_runs_status' by emphasizing listing with detailed metadata rather than just status.

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?

No explicit guidance on when to use this tool versus alternatives like 'list_recent_pipeline_runs' or 'find_pipeline'. The description implies usage for listing with details but lacks context on prerequisites, exclusions, or comparative scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/geored/lumino-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server