Skip to main content
Glama

find_singers_for_artist

Read-only

原曲アーティスト名から、そのアーティストの曲をよく歌うVSingerを探す(歌唱回数の多い順・部分一致)。「YOASOBIの曲をよく歌う歌い手は?」「自分の曲調に合う歌い手を探したい(似たアーティスト名で検索)」に答える用途。各歌い手について直近30日の歌唱数・最終歌唱日時・よく歌う曲(最大3曲)を返す。プロフィール・SNSリンクは get_singer で取得する。

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_singers_for_artist"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
artistYes
contextNoこのツールを呼ぶ目的やユーザーの依頼の要約(1文・任意)。検索品質の改善のためのログに記録されます

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe, closed read (readOnlyHint=true, openWorldHint=false, destructiveHint=false), so the bar is lower. The description still adds real behavioral context beyond them: result ordering, partial-match semantics, the 30-day window, and exactly which aggregate fields come back, though it says nothing about pagination or result caps.

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 core action, then use cases, then return shape, then the sibling pointer — a logical order with no filler. Slightly dense single block, but every sentence carries 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?

No output schema exists, and the description compensates by enumerating returned fields (30-day count, last sung timestamp, up to 3 songs). Combined with annotations, use cases, and the get_singer escape hatch, an agent has everything needed to call it correctly.

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 only 33% (only the context param is documented), so the description must compensate. It does: 'artist' is clarified as an original artist name with partial matching, and the ordering/return shape imply what the result set looks like. The 'limit' parameter (1-50) is never mentioned, leaving a gap.

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+resource: find VSingers who frequently cover songs by a given original artist, ranked by singing count, with partial matching. The two example queries and the explicit handoff to get_singer make it distinguishable from search_singers/similar_singers/top_singers without opening any 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?

Gives concrete use cases ("which singers cover YOASOBI?", "find singers matching my style via similar artist names") and explicitly routes profile/SNS lookups to get_singer. It stops short of stating when NOT to use it (e.g., searching by singer name instead of artist), so not a full 5.

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