Skip to main content
Glama

get_singer

Read-only

歌い手IDで VSinger のプロフィール(説明・SNSリンク・YouTubeチャンネル)と歌唱統計を取得する。displayName は装飾を外した表示名(無ければ null)。

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": {
      "singerId": "<singerId>"
    },
    "name": "get_singer"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses the returned content (profile fields, SNS links, YouTube channel, singing statistics) and a concrete null contract for displayName. It does not cover error behavior for an invalid ID, which keeps it from 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.

Conciseness5/5

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

Two sentences with no filler. The retrieval scope is front-loaded, and the displayName clarification follows as a compact secondary note.

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 carries the burden of describing returns and does so by enumerating the profile components and statistics. Combined with annotations covering the safety profile, an agent has enough to call it correctly; only error/missing-ID behavior is absent.

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 coverage is 50%: the context parameter is fully documented in schema while singerId has no schema description. The description partially compensates by framing singerId as a VSinger singer ID used for direct lookup, but adds no format or validation detail beyond that, so baseline 3 applies.

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 names a specific verb and resource: fetch a VSinger profile (description, SNS links, YouTube channel) plus singing statistics by singer ID. That clearly separates it from search_singers, top_singers, and random_singer, which do not take a single ID. It stops short of explicitly naming an alternative, so it is not quite 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 Guidelines3/5

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

The phrase '歌い手IDで' implies a direct ID lookup, which tells the agent this is a by-ID fetch rather than a search. There is no explicit when-to-use versus when-not-to-use guidance, no note on what to do when the ID is unknown (e.g. use search_singers first), and no prerequisites stated.

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