Skip to main content
Glama

pare-suitengumae.jp

サイトの中を探す

search
Read-only

「pare-suitengumae.jp」(pare-suitengumae.jp)から読み込んだページの中を言葉で探し、当てはまる箇所を抜粋と URL つきで返します。pare-suitengumae.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?

Beyond the annotations, the description discloses important behavior: only already-loaded pages are searchable, the entire internet and post-load updates are excluded, and results include excerpts and URLs. It also tells the agent how to behave on failure, including not guessing and reporting that the site did not contain the answer. This is substantial behavioral context that annotations alone do not provide.

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?

The description is front-loaded with purpose, scope, and return behavior, then provides fallback guidance. Most sentences earn their place, though the repetition of the domain name and the detailed failure procedure make it slightly longer than strictly necessary. Structure is otherwise clear and easy to follow.

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?

Given that annotations cover safety and read-only behavior and an output schema exists, the description provides everything an agent needs to call this tool correctly. It explains scope, intended use, fallback behavior, and the limitation that only loaded pages are searchable. No critical context appears to be 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?

Schema coverage is 100%, so the input schema already documents the single query parameter and gives an example. The description adds search-strategy guidance such as trying synonyms or expanded abbreviations, but it does not add syntax or format details beyond the schema. A baseline 3 is appropriate.

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 clearly states a specific verb and resource: search within pages loaded from pare-suitengumae.jp and return matching excerpts with URLs. It also defines scope by excluding the wider internet and later updates. However, it does not explicitly distinguish this tool from similarly named siblings such as search_pages, so it falls short of a 5.

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?

It gives clear usage guidance: when asked about pare-suitengumae.jp, use this first. It also describes what to do when results are not found, including rephrasing, expanding abbreviations, using synonyms, and reading returned page candidates. It does not name alternative tools or explicitly say when another sibling should be used instead.

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