Skip to main content
Glama

klanex

by io.github.chrassy

list_executions

List this account's executions, newest first, optionally filtered by status or a created_at time range. Returns next_cursor when a page is full; pass it back as cursor for the next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNopage size, 1-100 (default 20)
sinceNoonly executions created at or after this RFC3339 timestamp
untilNoonly executions created before this RFC3339 timestamp
cursorNoopaque next_cursor value from a previous page
statusNofilter by status: QUEUED, RUNNING, RETRYING, SUCCEEDED, or FAILED

TDQS

A4.4/5.0
Behavior4/5

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

Discloses pagination (next_cursor), ordering (newest first), and optional filters. No annotations provided, so description carries burden; does not mention auth or rate limits, but adequate for a listing tool.

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?

Two concise sentences, front-loaded with purpose and ordering, no superfluous text.

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?

Covers pagination, ordering, and filtering. Lacks explicit response format, but given no output schema and clear parameter descriptions, it is sufficiently complete.

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 covers all 5 parameters with descriptions. Description adds context on pagination flow and ordering, enhancing understanding beyond schema.

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?

Description clearly states it lists executions, ordered newest first, with optional filters. Distinguishes from siblings like execute, get_execution, etc.

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

Usage Guidelines4/5

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

Explains when to use for paginated listing and filtering. Implicitly distinguishes from single-execution retrieval, but no explicit when-not or alternatives.

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

All klanex toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: execute, get_execution, get_usage, list_connections, list_executions, replay_execution. No overlapping functionality; descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (execute, get_execution, get_usage, list_connections, list_executions, replay_execution). Naming is uniform and predictable.

Tool Count5/5

Six tools cover the core functionality of an execution management server: initiating, checking, listing, replaying executions, plus managing connections and usage. This is well-scoped, not too few nor too many.

Completeness5/5

The tool set provides a complete lifecycle for asynchronous API execution: create (execute), check status (get_execution), list (list_executions), replay (replay_execution), manage credentials (list_connections), and monitor usage (get_usage). No obvious gaps for the stated domain.

Resources