Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Find SoundCloud songs for an alarm's sound

find_soundcloud_song
Read-only

Finds songs on SoundCloud to use as an alarm's sound: by a style ("lofi", "hip hop", "morning"), an artist or a song's name, or a SoundCloud link (a track is that song; an artist's profile is their songs). Only songs that play in full. For picking a sound, not for an alarm on an artist's new music. Returns up to 5 songs, most played first, each with its id (soundcloud:track:N, for set_media with use song), title, artist, length, plays and link. No match returns a note.

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": {
      "search": "<search>"
    },
    "name": "find_soundcloud_song"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchYesA style, an artist or a song as the person said it, "lofi" or "fred again marea", or a SoundCloud link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: results are limited to fully playable songs, capped at 5, ordered by play count, and an empty result yields a note rather than an error. Only the parenthetical id/field list overlaps with what an output-oriented reader might expect elsewhere.

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 purpose, then input forms, then exclusion, then return shape — a sensible order with no filler sentences. The nested parentheticals make it slightly dense, but every clause carries information an agent needs.

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, and the description compensates fully by naming the returned fields (id format soundcloud:track:N, title, artist, length, plays, link), the result cap and ordering, and the no-match case. Combined with the annotations, nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema does not: a link can be a track (that song) or an artist's profile (their songs), and styles are exemplified ("lofi", "hip hop", "morning"). That disambiguates how the single free-text parameter is interpreted.

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 ("Finds songs on SoundCloud") scoped to a concrete purpose ("to use as an alarm's sound"). The parenthetical enumerates the accepted input forms, and the mention of artist profiles vs tracks separates it from the sibling find_soundcloud_artist.

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 an explicit exclusion: "For picking a sound, not for an alarm on an artist's new music," which rules out the follow-artist use case. It clarifies the input shapes but never names the sibling tool an agent should call instead for those other cases, so routing is implied rather than stated.

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