Skip to main content
Glama
Sign In
Metrx MCP Server

Metrx MCP Server

by metrxbots
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Acknowledge Alert

metrx_acknowledge_alert
Idempotent

Marks one or more alerts as read or acknowledged, removing them from the unread list while preserving history. Use it after acting on an alert; it does not resolve the underlying issue.

Instructions

Mark one or more alerts as read/acknowledged. This removes them from the unread alerts list but preserves them in history. Do NOT use for resolving the underlying issue — take action on the alert first. Requires an API key with the 'write' scope.

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": {
      "alert_ids": "<alert_ids>"
    },
    "name": "metrx_acknowledge_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idsYesAlert IDs to acknowledge

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already state readOnly=false, destructive=false, and idempotent=true, and the description adds meaningful context on top: the effect is removing items from the unread list while preserving them in history, and a write-scope credential is required. That tells the agent exactly what mutates and what survives, which is the key behavioral risk for an acknowledge operation.

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?

Three short sentences, each doing distinct work: what it does, its side effects, then the usage prohibition and auth prerequisite. Nothing is repeated and the core action is front-loaded.

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 one-parameter mutation with no output schema, the description covers action, side effects, misuse avoidance, and auth requirements. There is no material gap an agent would need filled before calling it correctly.

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% and the single alert_ids array is documented with type, item format, and 1–50 bounds in the schema itself. The description only echoes the batch nature ('one or more alerts') without adding syntax, ordering, or partial-failure semantics, so it meets but does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Mark one or more alerts as read/acknowledged') and implies batch scope, which an agent can immediately match against a task like 'clear my unread alerts'. It does not explicitly name a sibling (e.g., metrx_get_alerts) for contrast, so it stops short of a 5.

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?

It gives a clear negative rule ('Do NOT use for resolving the underlying issue — take action on the alert first') and a prerequisite (API key with 'write' scope), which is real when-to-use guidance. It does not point to the read-side alternative for inspecting alerts, so it is not fully exhaustive.

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