Skip to main content
Glama

Create a paused alert

approve_alert_creation
DestructiveIdempotent

Create the quoted alert, paused. Call only after the person accepts the monthly minimum shown in the quote. Starts no checks: to turn it on, use quote_resume and resume_alert (runs until paused), or quote_monitoring and approve_monitoring (with an end date and ceilings).

Permission: monitoring:manage. Ask the person before calling.

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>",
      "request_hash": "<request_hash>"
    },
    "name": "approve_alert_creation"
  }
}

Input Schema

NameRequiredDescriptionDefault
creation_idYesThe creation ID returned when it was quoted or created.
request_hashYesThe exact request_hash from the quote. Approval fails if anything changed since the quote.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that no checks start ('Starts no checks'), the required permission scope (monitoring:manage), the consent requirement, and the commercial consequence (monthly minimum). This is important context for a destructive/write operation that the annotations alone (destructiveHint=true, idempotentHint=true) cannot convey.

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?

Three tight sentences, front-loaded with the action and its state, then the precondition, then the activation alternatives and permission. No filler; the parentheticals carry real constraints rather than padding.

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

Completeness5/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 described. Combined with the stated permission, consent precondition, paused-state behavior, and activation paths, an agent has everything needed to call this safely and correctly.

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%, including the critical note that approval fails if anything changed since the quote. The description adds only ambient context ('the quote') rather than parameter-level meaning, so the schema carries the load and the baseline 3 applies.

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

Purpose5/5

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

Specific verb and resource ('Create the quoted alert') plus a crucial scope qualifier ('paused'). The distinction from siblings like resume_alert and approve_monitoring is made explicit, so an agent can select it without inspecting schemas.

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

Usage Guidelines5/5

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

States a hard precondition ('Call only after the person accepts the monthly minimum shown in the quote') and an explicit routing rule: to actually start monitoring, use quote_resume/resume_alert or quote_monitoring/approve_monitoring. Naming the alternatives and the condition that selects them is exactly what is needed.

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