Skip to main content
Glama

random_singer

Read-only

VSinger をランダムに1名紹介する(毎回等確率・一期一会)。「誰かおすすめして」「新しい歌い手と出会いたい」に答える用途。プロフィール・歌唱統計と直近の歌唱(最大3件)を返す。displayName は装飾を外した表示名(無ければ null)。下限フィルタ(minTotalSongs / minTotalStreams / minStreamsLast30Days)を指定すると、その条件を満たす歌い手の中から等確率で抽選できる(singer_stats ベース・1日1回更新・公開中の歌唱のみを集計)。

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": "random_singer"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's remaining value is stochasticity and data provenance. It does disclose equal-probability sampling ('毎回等確率・一期一会'), that filtering is drawn from singer_stats, that stats update once daily, and that only public performances are counted. That is genuinely useful extra context beyond the annotations, but the return shape and any edge case (e.g., empty filtered pool) are not described.

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?

One dense paragraph that front-loads the core purpose and the intent triggers before the filter mechanics. Parenthetical asides about the stats basis are somewhat compressed but still earn their place; nothing is wasted, though readability would improve with sentence breaks.

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?

There is no output schema, and the description compensates by enumerating the returned content (profile, stats, up to 3 recent performances) and clarifying the displayName field's nullability. For a 4-parameter read-only randomizer that is close to complete; only filter edge-case behavior is left implicit.

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 description coverage is only 25% (only `context` is documented), so the three min* parameters carry no schema text. The description helps by naming them as lower-bound filters and explaining they are evaluated against singer_stats with daily refresh, which clarifies their meaning collectively, but it never explains what each threshold counts or what happens when the filter excludes everyone.

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?

The description states a specific verb and scope: 'VSinger をランダムに1名紹介する' with equal probability, and lists what is returned (profile, singing stats, up to 3 recent performances). This clearly separates it from catalog-style siblings like search_singers or top_singers, though it never names an alternative explicitly.

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 usage triggers ('誰かおすすめして', '新しい歌い手と出会いたい'), which tells the agent exactly which user intents this answers. It stops short of stating when not to use it or naming a sibling to use instead, so the routing guidance is clear but not exhaustive.

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