Skip to main content
Glama

Get execution trends

get_execution_trends
Read-only

Aggregate deployment/platform execution history for this cluster over a time window (default 7 days): totals by status and type, failure rate, the most-failing execution names, and the most recent failures with error excerpts. Use this to answer 'has this been failing for a while', 'what keeps breaking', and to correlate an incident's start time with deploys. For a single execution's step detail use get_execution_details instead. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cluster_id": "<cluster_id>"
    },
    "name": "get_execution_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter to one execution type (e.g. update_stack, install_addon).
cluster_idYesAnkra cluster id (UUID) the call targets. Discover ids with list_clusters.
window_daysNoLook-back window in days (default 7).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and the description confirms 'Read-only', so there is no contradiction and safety is doubly clear. Beyond the annotation it discloses the aggregation shape, the default 7-day window, and that error excerpts are included, which is real behavioral value. It stops short of stating cost/latency or that a 30-day window cap exists (that lives only in the schema), so it is strong but not exhaustive.

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?

The purpose and scope are front-loaded, and each subsequent sentence adds routing or content information. It is slightly dense with a long output enumeration sentence, but no wording is redundant with the exception of the trailing 'Read-only', which restates readOnlyHint at negligible cost.

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, and the description compensates by enumerating the aggregate fields an agent will receive, so the caller knows what to expect without guessing. For a low-complexity read-only aggregation tool with 3 fully documented parameters, nothing material needed to invoke or interpret it is missing.

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 all three parameters (type, cluster_id, window_days) are already documented in the schema, including the 1-30 bounds and the UUID/discovery hint. The description adds only the default window value, which the schema also states, so baseline 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?

The description gives a specific verb (aggregate) and resource (deployment/platform execution history for a cluster over a time window) and enumerates the concrete outputs: totals by status and type, failure rate, most-failing names, and recent failures with error excerpts. That is enough for an agent to distinguish it from list_recent_executions and get_execution_details without opening a 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?

It names the exact questions the tool answers ('has this been failing for a while', 'what keeps breaking', incident start-time correlation with deploys) and explicitly routes the agent elsewhere for the adjacent need: 'For a single execution's step detail use get_execution_details instead.' That is explicit when-to-use plus a named alternative, not implied 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.