Skip to main content
Glama
Sign In

LFG Alarm

by gm.lfg
OverviewDiscussionsAdmin

Find a SoundCloud artist

find_soundcloud_artist
Read-onlyIdempotent

Finds artists on SoundCloud by name, or the one artist a SoundCloud link (a profile or a track) belongs to. For picking the right artist before a drop alarm; it sets nothing. Many accounts share a name, so the person picks: returns up to 5 artists, most followed first, each with their followers, how many tracks they have, their profile link and their newest track. 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": {
      "artist": "<artist>"
    },
    "name": "find_soundcloud_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistYesThe artist's name as the person said it, "fred again", or a SoundCloud link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description still adds substantive behavior: caps results at 5, sorts by follower count, lists the exact fields returned per artist, and specifies that a miss returns a note rather than an error. That is genuinely useful beyond structured data.

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 what it does and keeps to three dense sentences with no filler. The semicolon-chained clauses make it slightly run-on, but each clause carries 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, and the description compensates by describing the return shape (count, ordering, per-artist fields, empty-result behavior). For a one-parameter read tool, nothing an agent needs in order to call it or interpret results 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 coverage is 100% and the schema already documents that the single parameter accepts a name or a SoundCloud link. The description reinforces the dual-mode input and the 'as the person said it' fuzziness that causes multiple matches, but adds little syntax or format detail beyond the schema.

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 (find artists on SoundCloud) and covers both input modes: a name, or a link to a profile or track. It also implicitly distinguishes itself from the alarm-setting siblings by noting it 'sets nothing'.

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?

States the workflow context explicitly ('For picking the right artist before a drop alarm') and explains the human-in-the-loop pattern when names collide ('Many accounts share a name, so the person picks'). It doesn't name a sibling alternative, but no sibling performs artist lookup, so the positioning is clear.

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