Skip to main content
Glama
Sign In
Metrx MCP Server

Metrx MCP Server

by metrxbots
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Alerts

metrx_get_alerts
Read-onlyIdempotent

Retrieve active alerts and notifications for an agent fleet, including cost spikes, error-rate increases, budget warnings, and system-health issues; filter results by severity.

Instructions

Get active alerts and notifications for your agent fleet. Includes cost spikes, error rate increases, budget warnings, and system health notifications. Optionally filter by severity. Do NOT use for forward-looking risk — use get_failure_predictions for that. Requires an API key with the 'read' scope.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "metrx_get_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of alerts to return
severityNoFilter by alert severity
unread_onlyNoOnly return unread alerts (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: the required API key scope ('read') and the breadth of alert categories returned. It stops short of describing result ordering or volume behavior, which keeps it from a 5.

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?

Four short sentences, purpose first, followed by content scope, the alternative-tool exclusion, and the auth requirement. The severity sentence is largely redundant with the schema, a minor wasted line, but nothing else is padded.

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?

For a read-only, zero-required-parameter listing tool with full schema coverage and no output schema, the description covers purpose, scope, exclusions, and the auth prerequisite. Nothing an agent needs in order to call it correctly 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%, so limit, severity, and unread_only are already fully documented. The description only echoes the severity filter ('Optionally filter by severity') without adding semantics such as default filtering or limit behavior. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource (get active alerts and notifications) plus the concrete content categories it covers: cost spikes, error rate increases, budget warnings, system health. It also explicitly distinguishes itself from the forward-looking sibling get_failure_predictions, so an agent can route without opening schemas.

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?

Contains an explicit exclusion with a named alternative: 'Do NOT use for forward-looking risk — use get_failure_predictions for that.' It also notes the optional severity narrowing, giving the agent both a when-to-use and a when-not-to-use signal.

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

Deploy Server

Other Tools