Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

See who is on an alarm

list_riders
Read-onlyIdempotent

Lists everyone on an alarm the person made or joined: each username and the day they joined, the creator first, then the newest. For people already on one alarm; people still asking to join are a separate list. Usernames only, nothing else about anyone. An alarm the person is not on returns an error.

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": "list_riders"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe alarm's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, yet the description adds genuinely new behavior: ordering (creator first, then newest), content restriction ('Usernames only, nothing else'), and a failure mode ('An alarm the person is not on returns an error'). These go beyond the structured hints, though permission nuances and error types remain unspecified.

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, no waste, and the core purpose is front-loaded before the ordering detail, exclusion, content limit, and error case. Every sentence contributes distinct information.

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?

There is no output schema, so the description must convey return content — it does (usernames plus join day, with explicit ordering) — and it also documents the error case for non-members. Nothing an agent needs to call 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 description coverage is 100% for the single 'id' parameter, so the schema already carries full parameter meaning. The description adds no extra detail about the id (e.g., where to obtain it) beyond what the schema provides, which is the expected baseline 3.

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 ('Lists everyone on an alarm the person made or joined') and immediately distinguishes the scope from a sibling concern by noting that pending requesters are 'a separate list.' An agent can tell this apart from list_join_requests without inspecting either schema.

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?

The exclusion 'For people already on one alarm; people still asking to join are a separate list' clearly signals when to pick this over the join-request counterpart. It stops short of naming the sibling tool outright or stating preconditions (membership required), but the routing context is explicit enough to act on.

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