Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Comment on an alarm

post_comment

Posts a comment on an alarm the person rides or made, as the person, from its link or code. For words; a heart is separate. Everyone who can open the alarm sees it, and its creator is told. Up to 280 characters.

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": {
      "link": "<link>",
      "comment": "<comment>"
    },
    "name": "post_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYesThe alarm's link or code.
commentYesThe comment, in the person's words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a non-destructive write (readOnlyHint=false), but the description adds real side-effect context: 'Everyone who can open the alarm sees it, and its creator is told.' That visibility and notification disclosure is valuable beyond the annotations, though it doesn't address duplicate-post behavior despite idempotentHint=false.

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-loads the action and packs scope, media distinction, distribution, and length into three tight sentences. The fragmented 'For words; a heart is separate' is slightly telegraphic but earns its place by routing away from hearting.

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 two-parameter, no-output-schema write tool with annotations present, the description covers scope, visibility, notification, and character limit. It leaves the error path for out-of-scope alarms (e.g. not a rider/creator) unspecified, a minor gap.

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%, so both parameters are already documented. 'From its link or code' and 'Up to 280 characters' merely echo the schema's 'link or code' and maxLength=280, adding little beyond structured data. Baseline 3 is appropriate.

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 (post) and resource (comment on an alarm) with a scope constraint (an alarm the person rides or made). It explicitly separates itself from the sibling heart_alarm with 'a heart is separate,' so an agent can distinguish the two without opening 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?

Points the agent to the alternative for reactions ('For words; a heart is separate') and scopes valid targets to alarms the person rides or made. Clear when-to-use context, though it doesn't spell out failure behavior for alarms outside that scope.

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