Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

See who woke up first

get_wake_board
Read-onlyIdempotent

Shows who got up and how fast, for alarms that rang: the order people got up in, their times from the ring, snoozes and titles (First up, Snooze champ, Buys coffee), and who is still asleep. For alarms that already rang; when an alarm rings next is on its card and in the alarm list. One alarm by id, or every alarm that rang for the person in the last 24 hours. Returns a note when nothing rang.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_wake_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOne alarm's id. When absent, every alarm that rang in the last 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral detail beyond that: it describes the returned wake-board data and notes that a note is returned when nothing rang.

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?

The description is front-loaded with the main value and remains reasonably compact. There is minor redundancy around 'alarms that rang' versus 'alarms that already rang,' and the second sentence is slightly awkward, but no major space is wasted.

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?

For a one-parameter read-only tool with no output schema, the description supplies the key context an agent needs: the scope, optional id behavior, return contents, and empty-result behavior. Nothing essential for correct invocation appears to be 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 description coverage is 100%, and the schema already explains that id selects one alarm while absence covers all alarms in the last 24 hours. The description restates that meaning but adds no format or syntax detail beyond the schema.

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 clearly states a specific verb and resource: it shows the wake-up order, timing, snoozes, and titles for alarms that already rang. It distinguishes this tool from alarm-card/alarm-list viewing of upcoming rings, but it does not name sibling tools directly.

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?

It says to use this for alarms that already rang, and points elsewhere for when an alarm will ring next. It also explains that omitting the id returns every alarm that rang for the person in the last 24 hours, though it does not explicitly name sibling tools.

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