Skip to main content
Glama

Quote monitoring limits

quote_monitoring
Idempotent

Quote a fixed-term monitoring permission for a paused alert: an expiry within 30 days, a total ceiling (including the minimum) and a per-check ceiling. Starts 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": {
      "alert_id": "<alert_id>",
      "expires_at": "<expires_at>",
      "maximum_charge_micros": "<maximum_charge_micros>",
      "maximum_operation_micros": "<maximum_operation_micros>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "quote_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesPaused alert ID.
expires_atYesUTC expiry with milliseconds, for example 2026-12-01T00:00:00.000Z. Within 30 days and before the key expires.
idempotency_keyYesA new random key (16–100 letters, digits, - or _) for each request. Reuse it only to retry the identical request.
maximum_charge_microsYesTotal ceiling in USD micros, including the minimum.
maximum_operation_microsYesCeiling per check in USD micros.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations declare non-read-only, idempotent and non-destructive, and the description goes beyond that by stating nothing is started, that the expiry must fall within 30 days, and that the total ceiling includes the minimum charge. The one gap is retry/idempotency behaviour, which is left entirely to the schema.

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?

Two short sentences: the first defines the operation and its limits, the second kills the main misreading ('Starts nothing'), and the permission note sits last. No filler.

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 five fully described required parameters and an output schema, the description only needs to carry scope and preconditions, which it does (paused alert, permission, 30-day expiry). Only the sequencing relative to approve_monitoring and retry behaviour remain implicit.

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 expiry window, micros units and idempotency-key rules are already documented per parameter. The description restates the 30-day window and the 'including the minimum' ceiling nuance, adding emphasis but no genuinely new semantics beyond the schema.

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?

The description gives a specific verb and resource — quote a fixed-term monitoring permission for a paused alert — and adds 'Starts nothing', which separates it from the approve/revoke siblings at a glance. An agent can identify what this produces without opening the schema.

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?

'Starts nothing' implies this is the step preceding approve_monitoring, and the required permission (monitoring:manage) plus the paused-alert precondition give real context. However, it never explicitly names when to pick this over the other quote_* variants, so the routing guidance is only implied.

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