Skip to main content
Glama

search_singers

Read-only

VSinger を名前・別名から探す。歌い手の ID が分からないときの入口。名前は表記のまま指定すること(内部で翻訳・ローマ字化はしない)。sortBy・下限フィルタ(minTotalSongs / minTotalStreams / minStreamsLast30Days)を指定すると、名前・別名一致の中から活動量で絞り込み・並べ替えできる(singer_stats ベース・1日1回更新・公開中の歌唱のみを集計)。指定時の結果には stats(totalStreams 等)が付く。純ランキングは top_singers を使う。displayName は装飾を外した表示名(無ければ null)。結果の shortDescription は短い紹介文のみで、プロフィール全文・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": {
      "query": "<query>"
    },
    "name": "search_singers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
sortByNo並べ替え軸(任意)。streamsLast30Days=直近30日の歌唱数 / totalStreams=総歌唱数(全期間累計)/ totalSongs=レパートリー数。未指定なら名前順
contextNoこのツールを呼ぶ目的やユーザーの依頼の要約(1文・任意)。検索品質の改善のためのログに記録されます
minTotalSongsNo
minTotalStreamsNo
minStreamsLast30DaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds real behavior beyond that: name matching is literal with no internal translation or romanization, filtering runs on singer_stats that updates once daily and counts only public streams, and stats fields appear only when sort/filter params are set. It also discloses that shortDescription is truncated to a short blurb and that displayName can be null, which tells the agent what it will and won't receive.

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?

Roughly five sentences, front-loaded with the core purpose before routing to alternatives and then disclosing filter semantics. Dense parenthetical asides (e.g., the singer_stats update note) are informative but make the text slightly heavy; nothing is purely redundant.

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?

For a 7-parameter, no-output-schema search tool, the description explains the matching rule, the filter/sort behavior, the stats update cadence, and what the main return fields contain (displayName, shortDescription, stats). Only limit and context go undescribed.

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 29%, so the description carries real weight: it explains that query must be specified as written, and that sortBy plus the three min* thresholds filter and reorder within name/alias matches against singer_stats. It leaves limit and context unexplained, so one star is deducted despite the strong coverage of the semantically hard parameters.

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?

The description opens with a specific verb and resource: "VSinger を名前・別名から探す" (find VSingers by name or alias), and it frames the tool's role as the entry point when the singer ID is unknown. It explicitly separates itself from top_singers (pure ranking) and get_singer (full profile and SNS links), so the agent can pick it without opening the schema.

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?

It states the triggering condition ("歌い手の ID が分からないときの入口") and routes to named alternatives for two adjacent needs: top_singers for rankings and get_singer for full bios and SNS links. This is explicit when/when-not guidance rather than implied usage.

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