Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Browse public alarms

browse_discover
Read-onlyIdempotent

Lists public alarms anyone can join, newest or most joined first, optionally matching words or of one kind: each one's name, creator, when it rings, riders, hearts and link. For public alarms by anyone; the person's own alarms are a separate list. Up to 25, 10 when not given. Returns a note when none match.

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

Input Schema

NameRequiredDescriptionDefault
kindNoOnly time, social (posts and streams), onchain (prices and trades) or music (an artist's new music on SoundCloud) alarms.
sortNorecent, or subscribers for the most joined.recent
limitNoHow many, up to 25.
searchNoWords to match, "launch", "lakers".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Only time, social (posts and streams) or onchain (prices and trades) alarms."New value: +"Only time, social (posts and streams), onchain (prices and trades) or music (an artist's new music on SoundCloud) alarms."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "time",
-  "social",
-  "onchain"
-]New value: +[
+  "time",
+  "social",
+  "onchain",
+  "music"
+]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by enumerating what each result carries (name, creator, ring time, riders, hearts, link), stating the default page size of 10 versus the 25 cap, and disclosing the empty-result behavior ("Returns a note when none match"). Annotations already cover the read-only/non-destructive profile, so this prose is genuine added context rather than repetition.

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?

Front-loaded with the core action and scope, then defaults and fallback behavior. The middle clause ("optionally matching words or of one kind") is slightly compressed to the point of awkwardness, and the page-size fact appears after more important scoping information.

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 no output schema, the description correctly compensates by listing returned fields, the default and maximum page size, and the no-match case. What remains unstated is purely minor — e.g. whether results are paginated beyond the limit or whether the search matches creator names as well as alarm names.

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%, so the enum meanings, defaults, and bounds are already documented in structured fields. The description restates the sort options and limit behavior in prose but adds no format or interaction detail the schema lacks — 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?

Names a specific verb and resource ("Lists public alarms anyone can join") and states the ordering, filtering, and result scope in the same breath. It explicitly separates itself from the personal-alarm sibling ("the person's own alarms are a separate list"), so an agent can route correctly without opening a 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?

Gives a clear selection rule: this tool is for public alarms by anyone, while the user's own alarms live in a different list. That is an explicit exclusion with an implied alternative, though it never names the sibling tool (list_my_alarms) directly, leaving a small inference step.

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