Skip to main content
Glama

公開トレンド資料のキーワード検索

search_tubesaku_context
Read-onlyIdempotent

TubeSakuの公開Markdownを横断的に読み、queryに関係しそうな本文を返す。 空白区切りの単純検索。queryは1〜500文字・1〜20語、同じ語の重複は除く。

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

Input Schema

NameRequiredDescriptionDefault
queryYes

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, idempotentHint=true and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the matching is a simple whitespace-delimited token search rather than semantic, and results are excerpts of likely-relevant body text rather than structured records. Result-count limits and ranking are still undisclosed.

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 short sentences with the purpose front-loaded and the query constraints second. Nothing is repeated from the schema and nothing is filler.

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 tool without an output schema, the description covers the input side well and states that body text is returned. It leaves open what a result actually contains — whether source document names or URLs accompany the excerpts, how many hits come back, and whether there is ranking — which an agent needs in order to chain a follow-up read_tubesaku_markdown call.

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 carries the full burden and does well: it states the query is split on whitespace, must be 1–500 characters and 1–20 words, and that duplicate terms are dropped. This is exactly the constraint information an agent needs to form a valid query, though it doesn't clarify case sensitivity or whether multi-word terms are ever treated as phrases.

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: a cross-cutting read over TubeSaku's public Markdown that returns body text matching the query. That clearly separates it from read_tubesaku_markdown and get_tubesaku_index, though those siblings are not named explicitly, so the 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?

'横断的に読み' (read across documents) implies this is the tool to use when you don't know which document holds the answer, as opposed to reading a specific file. However, there is no explicit when-to-use, no exclusions, and no mention of what to do if results are sparse or if a direct read would be better.

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