Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Ring a webhook alarm

ring_alarm

Rings one of the person's webhook alarms now, exactly as calling its private address does: everyone on it is woken, and calls within its quiet time after a ring are ignored. For an automation or agent acting for the person (a big sale, a new lead, a build that broke). Only webhook alarms the person made; other alarms ring on their own trigger. Returns how many people it woke, or when it can ring again.

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": {
      "id": "<id>"
    },
    "name": "ring_alarm"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webhook alarm's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare non-read-only, non-idempotent, non-destructive, open-world, but the description adds genuinely new context: everyone on the alarm is woken, and calls inside the quiet time after a ring are ignored — an effect plus a rate-limit-like suppression rule no annotation conveys. It also states the return value (how many people woke, or when it can ring again).

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?

Four sentences, front-loaded with the action and its equivalence to calling the private address; the side effects and scope restriction follow logically. Slightly dense but no sentence is filler.

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?

No output schema exists, yet the description explains the return value, the side effect on recipients, the quiet-time suppression, and the alarm-type restriction. Nothing material an agent needs to invoke this correctly is missing.

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 coverage is 100% for the single required uuid parameter, so the schema already carries the semantics. The description adds the ownership constraint ('one of the person's webhook alarms') but doesn't say how to obtain the id (e.g., via list_my_alarms), so 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?

States a specific verb and resource (ring a webhook alarm now) and explicitly scopes it to webhook alarms only, noting other alarm types ring on their own trigger. An agent can separate this from set_webhook_alarm or set_time_alarm without opening any schema.

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?

Gives concrete when-to-use guidance ('for an automation or agent acting for the person (a big sale, a new lead, a build that broke)') and an explicit exclusion ('only webhook alarms the person made; other alarms ring on their own trigger'). The condition that selects this tool over sibling alarm tools is stated outright.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LFG Alarm toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources