Skip to main content
Glama

Read one alert

get_alert
Read-onlyIdempotent

Read one alert you own, including edit_revision for edit_alert. Unknown alerts and other accounts’ alerts both return not_found.

Permission: alerts:read.

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": {
      "id": "<id>"
    },
    "name": "get_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAlert ID from list_alerts.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value beyond that: ownership scoping, the permission required (alerts:read), and the fact that other accounts' alerts return not_found rather than an authorization error, which is an important disclosure about information leakage. A 4 is defensible, but it does not cover response shape or any rate/consistency behavior, so it sits slightly above the annotation baseline rather than far beyond it.

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, front-loaded with the core action, then the downstream-use detail, then error semantics and the permission. No filler or restatement of the title beyond what is needed.

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?

For a single-parameter read tool with an output schema, the definition covers ownership scope, required permission, and error behavior, which is what an agent needs to invoke it correctly. Return values are adequately delegated to the output schema, leaving only minor unaddressed details.

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 the schema itself documents id as an 'Alert ID from list_alerts' with bounds of 1 to 2147483647. The description only adds the ownership constraint on that ID (unknown or foreign IDs yield not_found), which is useful but marginal. Baseline 3 applies when the schema carries the parameter documentation.

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?

States a specific verb and resource ('Read one alert') plus a scope constraint ('you own'), which separates it from the enumeration siblings such as list_alerts. It goes further by naming the key payload field (edit_revision) and its consumer (edit_alert), so an agent knows why this read matters, though it never explicitly points to list_alerts as the way to obtain an ID inside the description itself.

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?

Implies the primary usage context by tying the returned edit_revision to edit_alert, i.e. read here before editing. It also states the failure condition for IDs that are unknown or owned by another account, giving clear boundaries. It stops short of explicitly contrasting with list_alerts or stating when not to use it.

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