Skip to main content
Glama

Quote replacing an alert’s search

quote_alert_update
Idempotent

Quote replacing an alert’s whole search with a finished preview. Keeps result history, minimum and delivery preferences. Changes nothing yet.

Permission: monitoring:manage.

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_id": "<alert_id>",
      "preview_id": "<preview_id>",
      "notification_channel_ids": "<notification_channel_ids>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quote_alert_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesAlert ID.
preview_idYesThe preview ID returned when it was quoted or created.
idempotency_keyYesA new random key (16–100 letters, digits, - or _) for each request. Reuse it only to retry the identical request.
configuration_revisionNoRecommended: configuration_revision from get_alert_configuration.
notification_channel_idsYesChannel IDs from list_notification_connections. [] for none.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Adds real value beyond annotations: 'Changes nothing yet' resolves the tension between readOnlyHint=false and the fact that no state is mutated, and it enumerates what is preserved (result history, minimum, delivery preferences). It still says nothing about what the quote object contains, how long it lives, or what happens on a stale configuration_revision.

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, scoping statement first, behavioral guarantees second, permission last. No filler, though the permission sentence could sit in a consistent trailing position across the catalog (it does).

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 a full schema and an output schema present, the description only needs to carry scope, side-effect profile, and auth. It does all three, plus the preservation guarantees. The remaining gap is the relationship to the approving/cancelling siblings, which would let an agent place it in the workflow without guessing.

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%, so the baseline is 3 and the description adds nothing about individual parameters. There is even mild ambiguity: it says delivery preferences are kept while notification_channel_ids is a required argument, which the reader must reconcile from the schema.

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 action: quoting a replacement of an alert's entire saved search using a finished preview, which distinguishes it from creation-style siblings. The phrasing 'Quote replacing an alert's whole search' is precise about scope (whole search, not partial edit), though it never names the sibling used to confirm the change.

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?

'Changes nothing yet' implies this is a prepare/dry-run step taken before an approval tool, and 'Keeps result history, minimum and delivery preferences' hints at when it is appropriate. But it never states explicitly that an approval step must follow or how it differs from quote_alert_creation, so the agent must infer the workflow.

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