Skip to main content
Glama

サイトの中を探す

search
Read-only

「shikake101.co.jp」(shikake101.co.jp)から読み込んだページの中を言葉で探し、当てはまる箇所を抜粋と URL つきで返します。shikake101.co.jp について質問されたら、まずこれを使ってください。探せるのは読み込んだページだけで、ネット全体や、読み込んだあとの更新は含みません。見つからないときは、略語を正式な名前にする、同じ意味の別の言葉にするなど、言い方を変えて探し直してください。それでも見つからないときに返るページの候補も読み、それでも見つからなければ推測で答えず、このサイトの中では見つけられなかったと伝えてください。

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探したい言葉(例: 料金 支払い方法)

Output Schema

NameRequiredDescriptionDefault
resultsYes
candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, closed-world and non-destructive, yet the description adds substantive context beyond them: coverage is limited to already-loaded pages, live internet and post-load updates are excluded, and the failure mode returns page candidates rather than nothing. The explicit no-guessing instruction also sets a behavioral contract the agent would otherwise lack.

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-loads purpose and scope, then the usage policy, then fallback handling — a logical order with no filler. It runs somewhat long, and the rephrase/escalation guidance could be tightened, but every sentence carries operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 search with an output schema and rich annotations, this covers everything an agent needs: what is indexed, what is excluded, and what to do when results are empty. Return value explanation is not required given the output schema, so nothing important is missing.

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?

With a single required parameter at 100% schema description coverage, the schema already fully documents query, including an example. The description only implies that natural-language phrasing variations are valid search input, which adds marginal meaning beyond the schema, so the 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?

States a specific verb (search by word) and resource (pages loaded from shikake101.co.jp), plus the return shape (matching passages with excerpts and URLs). The scope is clear enough to distinguish it from fetch/get_page, but it does not address how it differs from the near-identically-named sibling search_pages, which is the main ambiguity an agent would face.

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 an explicit trigger (use first when asked about shikake101.co.jp) and a concrete escalation path: rephrase with full names or synonyms, then read the returned page candidates, then report not-found rather than guess. It does not name which sibling to use instead for other tasks such as fetching a known URL, so it stops short of full alternative routing.

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