Skip to main content
Glama

top_singers

Read-only

活動量の多いVSingerランキングを取得する。sortBy で直近30日の歌唱数(デフォルト・今活発な歌い手)・総歌唱数(全期間累計)・レパートリー数を選べる。統計は1日1回更新(statsAsOf が集計時点)で、公開中の歌唱のみを数えるため get_singer の統計とは数値が一致しないことがある。「最近活発な歌い手は?」「一番歌っている歌い手は?」に答える用途。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_singers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sortByNoランキング軸。streamsLast30Days=直近30日の歌唱数(デフォルト)/ totalStreams=総歌唱数(全期間累計)/ totalSongs=レパートリー数
contextNoこのツールを呼ぶ目的やユーザーの依頼の要約(1文・任意)。検索品質の改善のためのログに記録されます

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only/non-destructive safety, and the description adds genuinely new behavior: statistics refresh once per day, statsAsOf marks the aggregation time, only public streams are counted, and figures can diverge from get_singer. That freshness and data-scope disclosure is exactly the kind of context annotations cannot carry; only the result shape/pagination is left unstated.

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?

Three tight sentences: ranking purpose first, axis selection second, freshness/caveat third, with example intents last. Every sentence adds information, though the sortBy enumeration partially duplicates the schema.

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 read-only, non-destructive tool with no output schema and simple parameters, the description covers purpose, axes, freshness, and cross-tool caveats well. The remaining gap is result shape and default row count, which is minor but not nothing.

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 67% and the sortBy enum is already fully documented in the schema, so restating the three axes adds little. The description says nothing about limit (its default value or that the maximum is 50) or about what the context parameter does, leaving the undocumented parameter unimproved.

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 names a specific verb+resource (retrieving an activity-based VSinger ranking) and immediately scopes it with the three selectable ranking axes. It also distinguishes itself from sibling get_singer by warning that the statistics may differ, so an agent can tell the two apart without opening schemas.

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?

It gives concrete user intents this tool answers ("最近活発な歌い手は?", "一番歌っている歌い手は?") and maps the sortBy axis to which intent it serves, including that streamsLast30Days is the default for 'currently active'. It does not explicitly say when to prefer search_singers or get_singer instead, but the context is clear.

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