Skip to main content
Glama

Get Automations Metrics

automations_metrics_get
Read-onlyIdempotent

Returns aggregate automation run metrics for an app over the last 30 days (with the prior equal-length window for deltas): runs, runs_previous, success_rate, success_rate_previous, failures, median_run_time_ms, and p95_run_time_ms. Skipped runs are excluded. Takes the app_id returned by apps_list.

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": {
      "app_id": "<app_id>"
    },
    "name": "automations_metrics_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesThe app this call works on: its `app_id` uuid from `apps_list`.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / app_id / description
      Previous value: -"The app uuid returned by `apps_list`."New value: +"The app this call works on: its `app_id` uuid from `apps_list`."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: a fixed trailing 30-day window with an equal-length prior window for deltas, and that skipped runs are excluded from the counts.

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 sentences, front-loaded with the scope and window before the field list. Every clause carries information; nothing is filler.

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?

With no output schema, the description usefully enumerates the returned keys and the comparison window, which is the main thing an agent needs. Minor omissions remain (no statement of update cadence or timezone) but nothing essential for correct invocation 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 coverage is 100% and both parameters are documented in the schema, including the organization_id slug-resolution behavior. The description only repeats the schema's provenance hint that app_id comes from apps_list, adding no new parameter meaning.

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?

States a specific verb+resource (aggregate automation run metrics for an app), pins the window to the last 30 days, and enumerates the exact fields returned including the previous-window counterparts. An agent can distinguish this from a runs-listing tool purely from the text.

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?

Provides a prerequisite chain ("Takes the `app_id` returned by `apps_list`") which helps the agent sequence calls, but gives no when-to-use-vs-alternative guidance such as aggregate summary versus `automation_runs_list` for individual runs. Usage is implied by the 30-day window and aggregation, not stated.

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.

Resources