Skip to main content
Glama

top_songs

Read-only

歌唱回数の多い楽曲ランキングを取得する(全期間の累計・多い順)。「一番カバーされている曲は?」「みんながよく歌う曲は?」に答える用途。期間指定(直近30日の人気等)はできない。

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false), so the description's added value is the scope disclosure: results are cumulative across all time and sorted descending, and no time-window parameter exists. It does not disclose default result count or whether sing counts are returned, which are the remaining behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero filler: purpose and ordering first, then example use cases, then the exclusion. Everything is front-loaded and each sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 must carry the return-shape burden, and it only implies 'a ranked list of songs' without saying whether sing counts are included or what the default list size is. For a two-parameter, read-only ranking tool this is adequate but leaves the agent guessing on result volume and payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: `context` is documented in the schema, but `limit` carries only min/max bounds (1–50) with no description. The description says nothing about `limit` — not its default, not what happens when it is omitted — and adds no meaning beyond the schema's fixed ordering. It therefore fails to compensate for the coverage gap.

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 gives a specific verb+resource ('歌唱回数の多い楽曲ランキングを取得する') and pins down the ordering and scope (all-time cumulative, descending), which separates it from a plain keyword search like search_songs. It stops short of naming a sibling as the alternative for narrower queries, so it is clear but not fully differentiated.

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 supplies concrete user questions the tool answers ('一番カバーされている曲は?', 'みんながよく歌う曲は?') and an explicit exclusion: period-scoped popularity cannot be requested here. What is missing is a pointer to which tool an agent should reach for when a period filter is actually needed.

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