Skip to main content
Glama

get_song

Read-only

楽曲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": {
      "songId": "<songId>"
    },
    "name": "get_song"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The existing annotations already declare a safe read operation (readOnlyHint=true, destructiveHint=false, openWorldHint=false). Beyond those annotations, the description contributes useful content disclosure by saying the response bundles song details with singing history. It does not describe ordering, how many history entries appear by default, or what happens when no song matches the ID, so the additional behavioral value is moderate.

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?

It is one sentence with no wasted words, and the keying parameter is introduced first, followed by the two things returned. It is dense but readable; only the unqualified limit concept is left dangling.

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?

This is a read-only, single-key lookup with no output schema, so the description carries the burden of explaining the return shape. It does name the two return components, which is good, but it omits pagination and limit semantics and says nothing about error or empty-result behavior. That is adequate but not complete.

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?

Only 33% of the schema is described, and only context carries a schema description; limit and the format of songId are undocumented. The description clarifies that songId is a song identifier, but it never explains what limit controls (the maximum of 50 suggests a cap on singing-history entries), so it does not 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 uses a specific verb (取得する) and names both the resource and the key: song details such as the original artist plus singing history (who sang when), looked up by song ID. This clearly separates it from search-style siblings and singer-oriented siblings. It is unambiguous, though it does not explicitly name any sibling.

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

Usage Guidelines3/5

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

The description implies the precondition that you must already have a song ID, which distinguishes it from search_songs. However, it does not state when to choose it over neighbors such as search_songs, top_songs, or get_singer, and it offers no exclusions or prerequisites beyond that implied requirement.

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