Skip to main content
Glama

Read an alert update

get_alert_update
Read-onlyIdempotent

Read a replacement quote or its result. Changes nothing.

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": {
      "update_id": "<update_id>"
    },
    "name": "get_alert_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
update_idYesThe update ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so "Changes nothing" is largely redundant with structured data. The one genuinely additive piece is the explicit "Permission: monitoring:manage" requirement, which annotations do not convey; with an output schema present, return-format discussion is fairly excused. Beyond the permission line, the description adds little behavioral context.

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?

Two short sentences, front-loaded with the operation and followed by the effect and the permission, with no padding. The only dead weight is "Changes nothing," which restates readOnlyHint.

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 one-parameter, read-only tool with a documented schema and an output schema, the definition covers what matters: the effect, the permission, and where the ID comes from (via the schema). The remaining gap is routing guidance among the several alert-update siblings, which a more complete definition would supply.

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?

The single parameter update_id has full schema description coverage ("The update ID returned when it was quoted or created"), and the description adds nothing about it, nor does it need to. Baseline 3 applies when the schema fully documents the only parameter.

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

Purpose3/5

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

The description gives a verb ("Read") and an object ("a replacement quote or its result"), but "replacement quote" is ambiguous jargon that does not clearly map to the tool name get_alert_update, and the sibling quote_alert_update returns a quote too, so the agent cannot easily tell which produces the quote and which retrieves it. Neither the name nor the description differentiates this read tool from quote_alert_update or list_results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of the quote_alert_update/approve_alert_update siblings that generate or act on these updates, and no statement of when this tool should be preferred over list_results. The only context given is the required permission, which routes auth but not selection.

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