Skip to main content
Glama

オンライン学習講座 社員教育にも使える

サイトの中を探す

search
Read-only

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

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. Changed1 schema field changed
    • addedOutput schema / properties / candidates
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "title",
      +      "url"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already state readOnly/openWorld=false, and the description reinforces and enriches that: search coverage is limited to already-loaded pages, excludes live updates and the wider web, and it prescribes a no-answer behavior instead of hallucination. That is meaningful behavioral context beyond the structured fields.

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-loaded with purpose and scope, then progressive guidance for the failure path. It is longer than most definitions, but each sentence (scope limit, first-choice rule, rephrase strategy, no-result fallback) carries distinct operational value.

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 an output schema present, return values need no explanation, and the description covers coverage limits, when to invoke, and failure handling. The remaining gap is that it never clarifies its boundary against the near-identical `search_pages` sibling, nor that pages must be loaded first — though the latter is strongly implied.

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 100% with one well-described parameter, so the baseline is 3. The description goes further by explaining how to construct the query value (expand abbreviations to full names, substitute synonyms) when the first attempt fails, which adds strategy-level meaning the schema does not carry.

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?

Names a specific verb (探す) and an explicitly scoped resource (pages loaded from online.instantgakushu.jp), and specifies the return shape (抜粋 + URL). It does not, however, distinguish itself from the sibling `search_pages`, which an agent could easily confuse with this tool.

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 clear routing guidance ('オンライン学習講座 について質問されたら、まずこれを使ってください') plus a retry protocol (rephrase, expand abbreviations, use synonyms) and a terminal fallback (read suggested pages, then admit the site doesn't contain it rather than guessing). It never names an alternative sibling such as search_pages or fetch, so the when-not branch 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