Skip to main content
Glama

Quote creating an alert from a preview

quote_alert_creation
Idempotent

Quote creating a paused alert from a finished preview. Returns the monthly minimum and estimate. Nothing is charged or started.

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": {
      "preview_id": "<preview_id>",
      "notification_channel_ids": "<notification_channel_ids>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quote_alert_creation"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
notification_channel_idsYesChannel IDs. [] for none.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds meaningful behavior beyond that: the resulting alert is paused, the call returns the monthly minimum and estimate, nothing is charged or started, and the required permission is monitoring:manage.

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?

The description is four short sentences with no wasted wording. It front-loads the core action and prerequisite, then immediately states return values, safety characteristics, and the required permission.

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?

The tool is a mutation-style quote operation with a complete input schema and an output schema, and the description covers the key behavioral concerns: it requires a finished preview, creates a paused alert, charges nothing, and needs a specific permission. The main remaining gap is routing guidance against sibling preview and approval tools.

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 all three parameters are already documented in the schema, including preview_id, notification_channel_ids, and idempotency_key. The description does not add parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific action (quoting creation of a paused alert) tied to a specific input (a finished preview), and names the return values (monthly minimum and estimate). It is clear what the tool does, though it does not explicitly contrast itself with nearby siblings such as quote_preview or approve_alert_creation.

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?

Usage is implied by the prerequisite that the preview must be finished, and the statement that nothing is charged or started helps an agent understand this is a non-committal quote step. However, there is no explicit guidance on when to choose this versus quote_preview, approve_alert_creation, or get_alert_creation.

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