Skip to main content
Glama

Start paid monitoring

approve_monitoring
DestructiveIdempotent

Starts recurring paid checks and notifications within the quoted limits until expiry. Call only after the person approves the search, channels, expiry, ceilings and minimum. Failed checks are charged at cost plus margin.

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": {
      "monitoring_id": "<monitoring_id>",
      "request_hash": "<request_hash>"
    },
    "name": "approve_monitoring"
  }
}

Input Schema

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

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?

Beyond the annotations (destructiveHint=true, openWorldHint=true, idempotentHint=true), the description discloses the billing model — recurring charges plus 'failed checks are charged at cost plus margin' — and the required scope 'monitoring:manage' with a human-approval gate. That is real value-added context for a costly, destructive mutation, though it does not say what happens to already-charged cycles if the call is repeated.

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?

Four short sentences, front-loaded with purpose, then precondition, then cost caveat, then permission. Every sentence carries distinct information; nothing repeats the schema or annotations.

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 destructive, billable, human-gated mutation with an output schema and fully documented parameters, the description covers purpose, precondition, cost, and permission scope. The remaining gaps — idempotency behavior on retry and what the response contains — are partly handled by the annotations and output schema.

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%, with both request_hash and monitoring_id fully documented including the staleness rule. The description only gestures at these via 'within the quoted limits' and 'after the person approves', adding no syntax or validation meaning beyond the schema. Baseline 3 applies.

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 verb and resource — 'Starts recurring paid checks and notifications' — with a scope qualifier ('within the quoted limits until expiry'). It implicitly distinguishes this from quote_monitoring by requiring prior approval of the quote, though it never names the sibling that produces the quote or the one that stops monitoring.

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

Usage Guidelines4/5

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

Gives an explicit precondition: call only after the person approves the search, channels, expiry, ceilings and minimum, reinforced by 'Ask the person before calling.' It stops short of naming alternatives (e.g. quote_monitoring to obtain the request_hash, revoke_monitoring to undo), so the agent must infer the surrounding workflow.

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