Skip to main content
Glama

Read saved search settings

get_alert_configuration
Read-onlyIdempotent

Read one alert’s current source URLs, schedules, exact filters, matching brief, selected channels and minimum, plus configuration_revision. Use the revision to make sure settings have not changed before quoting a replacement. Never returns credentials or recipients.

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_configuration"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive, so the bar is lower, and the description still adds real value: it discloses that credentials and recipients are never returned, that a revision token is supplied for staleness checks, and that the call requires the alerts:read permission.

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 returned fields are front-loaded in the first sentence, the revision-use guidance follows, and the security caveat and permission line are short and purposeful. Slightly dense enumeration, but no sentence 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 an output schema, full annotation coverage and complete parameter documentation, the description only needs to add workflow and safety context, which it does. Nothing critical is missing, though error behavior for an unknown alert id is not addressed.

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 parameter is documented as 'Alert ID from list_alerts', so the schema already carries the semantics. The description adds nothing about the id, and the configuration_revision detail belongs to output rather than input, leaving this at 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 gives a specific verb (Read) and resource (one alert's configuration), then enumerates exactly what is returned: source URLs, schedules, exact filters, matching brief, channels, minimum and configuration_revision. This makes it clearly distinguishable from a generic alert fetch like get_alert, though it never names that sibling to sharpen the contrast.

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?

One concrete usage context is given: use configuration_revision to verify settings have not changed 'before quoting a replacement', which ties it to the quote/before-edit workflow. There is no explicit statement of when to use get_alert instead of this tool, and no exclusions.

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