Skip to main content
Glama

search

Read-only

VSinger Moment の歌唱パフォーマンスを横断検索する(deep research 互換)。曲名・歌い手名・原曲アーティストで検索できる(配信タイトルは検索対象外)。キーワードは原題の表記のまま指定すること(内部で翻訳・ローマ字化はしない。日本語曲は日本語、英語曲は英語のまま)。結果の id は fetch でそのまま詳細取得できる。

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: which fields are indexed, that stream titles are not searched, that no translation or romanization happens internally, and that ids interoperate with fetch. It omits result-count limits and pagination behavior.

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?

Front-loaded with purpose, then constraints, then the fetch hand-off, with no filler sentences. The parenthetical asides are dense but each carries actionable information about matching rules.

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 single-parameter, non-destructive search tool with no output schema, the description covers search scope, exclusions, query-format rules, and how to use the returned ids. Missing only result-set size or pagination details, which is a minor gap at this complexity.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry the parameter meaning, and it does: the single query string is matched against song title, singer name, and original artist, and must be given in the original title's notation with no translation or romanization. That is meaningful semantics well beyond the bare string schema.

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?

States a specific verb and resource: cross-searching VSinger Moment singing performances, with the searchable fields enumerated (song title, singer name, original artist). It also carves out stream titles as out of scope, which sharpens the boundary. It does not explicitly distinguish itself from siblings like search_songs or search_singers, so it falls short of a 5.

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?

Gives clear usage context: use it to find performances by song/singer/artist, and it explicitly excludes stream titles from matching. It also explains the downstream step, that returned ids can be passed straight to fetch. It stops short of naming when a sibling (search_songs, search_singers) would be the better choice.

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