Skip to main content
Glama

Read an alert creation

get_alert_creation
Read-onlyIdempotent

Read a creation quote or the paused alert it created. 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": {
      "creation_id": "<creation_id>"
    },
    "name": "get_alert_creation"
  }
}

Input Schema

NameRequiredDescriptionDefault
creation_idYesThe creation ID returned when it was quoted or created.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so "Changes nothing" is mostly redundant. The definition does add value beyond the annotations by disclosing the required permission (monitoring:manage) and by clarifying that the result may be a pre-creation quote rather than a live alert, which the annotations do not say.

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, front-loaded sentences with the resource first and the permission constraint second. The only wasted clause is "Changes nothing", which restates readOnlyHint rather than adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the permission requirement is covered. What is missing for a tool sitting among approve/cancel/quote siblings is routing guidance explaining why an agent would pick this read over get_alert or when it should quote instead.

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 only parameter (creation_id) is fully documented in the schema as the ID returned at quote/create time. The description adds no additional syntax, format, or sourcing nuance, so this is the baseline case where the schema does the work.

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?

"Read a creation quote or the paused alert it created" states a specific verb and names the two possible resources returned, which separates it from get_alert (reads an existing alert) and get_alert_creation's write siblings. It stops short of a crisp single-resource statement, since it's unclear whether the endpoint returns one or the other depending on state.

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 explicit when-to-use or when-not-to-use guidance. The definition never contrasts itself with get_alert, quote_alert_creation, or approve_alert_creation, so an agent must infer from the verb that this is the lookup after quoting/creating.

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