Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

genius_get_artist

Read-onlyIdempotent

Fetches a Genius artist profile by ID, returning artist details for use in UnClick MCP Server automation and AI agent workflows.

Instructions

Get a Genius artist by ID.

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": {
      "id": "<id>"
    },
    "name": "genius_get_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
api_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no behavior on an unknown ID, no note about the api_key parameter, no rate-limit or auth context despite openWorldHint=true.

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?

A single short sentence with the resource and key front-loaded and zero filler. Brevity is fine, though it shades into under-specification rather than being genuinely economical.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and has no output schema, but with 0% schema coverage and an undocumented api_key parameter, the description leaves an agent without enough information to invoke it confidently in this large toolset.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. 'By ID' partially explains the id parameter's meaning, but the undocumented api_key string parameter is left entirely unexplained — the agent cannot tell whether it is required, optional, or how to source it.

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 verb ('Get') and resource ('Genius artist') plus the lookup key (by ID), so the operation is unambiguous. It does not differentiate from nearby siblings such as genius_search, genius_get_song, or genius_artist_songs, so it falls short of a 5.

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?

No indication of when to prefer this over genius_search or genius_artist_songs, and no prerequisite stated (e.g., that you must already have a numeric Genius artist ID from a search). The agent must infer that a prior lookup is required.

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

Deploy Server

Other Tools