Skip to main content
Glama

search_songs

Read-only

歌唱パフォーマンスを検索する。曲名・歌い手名・原曲アーティストを横断し、誰がいつどの配信でその曲を歌ったかを返す(配信タイトルは検索対象外)。キーワードは原題の表記のまま指定すること(内部で翻訳・ローマ字化はしない。日本語曲は日本語、英語曲は英語のまま)。

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
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?

The annotations already declare a safe read-only, closed-world operation, so the description rightly focuses on behavior instead. It discloses two traits annotations cannot: that stream titles are outside the index, and that no internal translation or romanization occurs, which materially affects how queries must be formed. It does not mention result ordering, pagination, or empty-result behavior, which keeps it below a 5.

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 sentences with a clear front-loaded purpose statement, followed by return shape and scope exclusion, then the query-format constraint. Every sentence contributes and nothing is repeated from the name. The nested parentheticals make it slightly dense but not wasteful.

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?

With no output schema, the description correctly supplies the qualitative return shape (singer, date, stream) and clarifies what is not indexed. Combined with annotations covering the safety profile, an agent has enough to call it correctly. The only gap is the unmentioned limit semantics, which is minor for a search tool capped at 50.

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 33%, so the description carries extra weight. It compensates well for the required query parameter by explaining that it matches across three fields and must be written in the original script with no translation or romanization. The limit parameter is never addressed in the description and has no schema description, leaving its default and truncation behavior unexplained.

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 opens with a specific verb and resource (歌唱パフォーマンスを検索する) and enumerates the searchable fields — song title, singer name, original artist — plus the shape of the result (who sang what, on which stream, when). It also carves out scope by excluding stream titles from the search, which implicitly separates it from a general search tool. It never names a concrete sibling such as search or search_singers, so differentiation is inferred rather than stated.

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?

Usage is implied by the field list and the explicit exclusion of 配信タイトル, which hints that stream-title lookups belong elsewhere. The instruction to supply keywords in the original writing system is genuinely useful call-time guidance. However, there is no explicit statement of when to prefer this over search or search_singers, and no exclusions or prerequisites beyond the title-scope note.

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