Skip to main content
Glama

similar_singers

Read-only

指定した歌い手とレパートリー(歌う曲)が似ているVSingerを探す。「この歌い手が好きなら他は?」に答える用途。共通して歌っている曲数の多い順に返し、各歌い手について共通曲の例(最大3曲)も返す(クライアントLLMが「〇〇さんも『△△』を歌っています」のような推薦文を組み立てられる)。類似はレパートリー(歌う曲の重なり)のみに基づき、声質・ジャンルは考慮しない。共通曲が少ない(2曲未満の)歌い手は返らないことがある。singerId は search_singers / get_singer で得た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": {
      "singerId": "<singerId>"
    },
    "name": "similar_singers"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds substantial behavior beyond that: results are ordered by shared-song count descending, each entry includes up to 3 example common songs, similarity is repertoire-only (voice quality and genre ignored), and low-overlap singers may be omitted.

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 and use case, then return shape, then caveats. Dense but every sentence carries information; the parenthetical about composing recommendation text is slightly verbose but justifies the example-songs return.

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?

With no output schema, the description fully covers what comes back (ordered list plus up to 3 example songs per singer) and the similarity basis. An agent has everything needed to call it and interpret results correctly.

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 only 33%, so the description must compensate. It does explain the origin of singerId, but the limit parameter (1-50) is undocumented in both schema and description, and no default or ordering interaction is stated. Partial compensation warrants a mid score.

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: find VSingers whose repertoire (songs sung) is similar to a given singer. It also frames the intent ("if you like this singer, who else?"), which distinguishes it from search_singers and find_singers_for_artist without needing their schemas.

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

Usage Guidelines5/5

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

Explicitly says when to use it (recommendation-style queries), where the singerId must come from (search_singers / get_singer), and the exclusion condition (singers with fewer than 2 shared songs may not be returned). Nothing is left to inference.

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