Skip to main content
Glama

fetch

Read-only

search が返した id(stream:/singer:/song:/video: 接頭辞付き)の詳細ドキュメントを取得する(deep research 互換)。

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 carried by structured data. The description adds value beyond that by specifying that the return value is a 'detailed document' keyed by a prefixed id, but it leaves the meaning of 'deep research 互換' unexplained and says nothing about what happens with a malformed or unknown prefix.

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?

A single front-loaded sentence that packs the source of the id, the accepted prefix forms, and the return type with no filler. The trailing parenthetical 'deep research 互換' is the only part that does not obviously earn 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?

For a one-parameter read-only tool with no output schema and covered safety annotations, the definition supplies the essential input contract and return type. It remains incomplete on the fetch-vs-typed-getter distinction and on failure behavior, which an agent would need to choose between the overlapping siblings.

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 description coverage is 0% for the single id parameter, so the description must carry the semantics, and it does: the parameter value is an id produced by search and must retain a stream:/singer:/song:/video: prefix. That is a genuine constraint not present in the schema, though it does not describe length or error behavior for violating the format.

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 (詳細ドキュメント), and constrains the input to ids returned by search carrying a prefix, so the tool can be understood without opening the schema. However, it never distinguishes itself from the equally plausible direct getters in the sibling set (get_singer, get_song), which fetch the same kinds of entities.

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?

It states a real prerequisite: the id must come from search and must include a stream:/singer:/song:/video: prefix. What it does not state is when to use this tool rather than get_singer or get_song, so the choice between the generic fetch and the typed getters is left to inference.

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