runs_retry_failures
Re-run only the failed responses of a run, optionally limited to specific response ids via "only".
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| only | No |
CompletionKit
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only describes the basic action but lacks behavioral details about run status changes, output, auth requirements, or side effects. Minimal transparency.
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?
Single sentence with no fluff, directly states the core functionality. Information is front-loaded and every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple retry tool with no output schema, but lacks details on result (e.g., returns updated run, modifies in place) and prerequisites. Could be more complete.
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 0%, so description must compensate. It explains the 'only' parameter as optionally limiting to specific response IDs, but does not explicitly describe the 'id' parameter (the run ID). Partial added value.
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 tool re-runs only failed responses of a run, which is a specific verb and resource. It distinguishes from sibling 'runs_rerun' which likely reruns all responses.
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?
The description implies usage for partial retry of failed responses via the 'only' parameter, but does not explicitly compare with alternatives like runs_rerun or runs_regrade. No when-to-use or when-not-to-use guidance.
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.
TDQS
B3/5.0
Disambiguation5/5
Each tool targets a distinct resource and action, with clear separation across agreements, datasets, judges, metrics, prompts, runs, tags, and usage. Even similar tools like datasets_create vs datasets_create_from_url and runs_generate vs runs_rerun are explicitly differentiated in their descriptions.
Naming Consistency5/5
The overwhelming majority of tools follow a consistent plural_resource_action snake_case pattern (e.g., datasets_create, metrics_update, runs_retry_failures). The only slight deviation is promptfoo_import, but it is still descriptive and does not break the overall predictability.
Tool Count1/5
With 54 tools, the server far exceeds the 25+ threshold considered too many, and approaches the 50+ extreme mismatch level. Even for a broad LLM evaluation platform, this count is excessive and likely to overwhelm agents, making tool selection more error-prone.
Completeness4/5
The toolset provides full CRUD for core resources (datasets, metrics, prompts, runs, tags) plus lifecycle operations like publish, generate, regrade, and retry. It also includes cross-cutting utilities (usage, import, provider credentials). Minor gaps exist, such as no update/delete for agreements and no cross-run response search, but these are non-essential for the primary workflows.