Skip to main content
Glama

FoxAPIs data sources

SoundCloud artist

soundcloud_artist
Read-onlyIdempotent

A SoundCloud artist: followers, track count, plays and profile details, from the artist name. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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

Input Schema

NameRequiredDescriptionDefault
artistYesFor example: "flume"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, open-world), and the description adds genuinely non-obvious context: a 2-credit cost per call, no charge when no data is returned, and a required FoxAPIs key. It does not describe pagination, rate limits, or result shape, so it stops short of a 5.

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?

Two short sentences with the data payload front-loaded and cost/auth constraints trailing. Nothing is redundant, though '(free to start)' reads as marketing filler rather than operational 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 one required parameter and no output schema, the description carries the burden of describing return content, and it does so by naming the specific fields returned. Auth and cost prerequisites are also covered, leaving only edge-case behavior (errors, empty results beyond billing) unstated.

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 single 'artist' parameter carries its own example ('flume'). The description only confirms that lookup is driven by artist name, adding no format or disambiguation rules beyond the schema — the expected baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (SoundCloud artist) and enumerates the returned data — followers, track count, plays, profile details — keyed by artist name. It is clear what the tool does, though it never distinguishes itself from the sibling lastfm_artist, which covers similar artist data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the obvious alternative (lastfm_artist). 'From the artist name' merely restates the input mode rather than advising selection, leaving the agent to infer when this tool beats a general artist lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources