Skip to main content
Glama

公開トレンド資料の読出し

read_tubesaku_markdown
Read-onlyIdempotent
llms.txtで公開されているTubeSakuのMarkdownファイルを読む。
path例: /llms/google_trends.md

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": {
      "path": "<path>"
    },
    "name": "read_tubesaku_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that content lives under the llms.txt publication path, which is useful context, but says nothing about error behavior for missing paths or what the returned Markdown looks like.

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?

Two short lines, front-loaded with the purpose followed by a concrete path example. No filler, though the wording is terse enough that a little more guidance could have been added without bloat.

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 simple read-only tool with strong annotations and no output schema, the core is present, but the agent still lacks the discovery workflow (where do valid paths come from?) and any description of the returned content or failure modes.

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 0%, so the description carries the burden for the single 'path' parameter. The example '/llms/google_trends.md' usefully conveys the expected format and prefix, but it does not state whether other prefixes exist or whether the path is relative, nor enumerate valid values.

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 ('読む'/read) and a specific resource (TubeSaku Markdown files published via llms.txt). It implicitly distinguishes itself from catalog/index/search siblings by being a direct file read, though it never names those siblings explicitly.

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

Usage Guidelines2/5

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

No statement of when to use this tool versus get_tubesaku_index, get_tubesaku_data_catalog, or search_tubesaku_context, and no prerequisite that a path must first be discovered through the catalog/index. The agent must infer the workflow.

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