Skip to main content
Glama

ぎんざ姿オンラインショップー極上の天然とらふぐと近江牛の味

サイトの中を探す

search
Read-only

「ぎんざ姿オンラインショップー極上の天然とらふぐと近江牛の味」(shop.ginzasugata.online)から読み込んだページの中を言葉で探し、当てはまる箇所を抜粋と 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. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuine behavioral context on top: the search corpus is frozen at load time (no internet, no later updates), results come back as excerpts with URLs, and the tool should not be used to answer from inference when nothing matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The tool's core function is front-loaded in the first clause, which is good. But the full shop name '「ぎんざ姿オンラインショップー極上の天然とらふぐと近江牛の味」' is repeated verbatim in the second sentence, padding the text, and the fallback instructions run long relative to a one-parameter tool.

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?

An output schema exists, so return-shape explanation is not needed, and the description correctly spends its words on scope limits, query strategy, and failure handling. Given a simple one-required-param search tool, this is complete enough. It could be stronger only by explicitly positioning itself against the sibling 'search_pages'.

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% for the single 'query' parameter, so the baseline is 3. The description goes beyond the schema's example ('料金 支払い方法') by telling the agent how to shape the query — substitute abbreviations with full names, try synonymous phrasing, and re-search — which is real added meaning for the only parameter.

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 states a specific verb and resource: it searches text within pages loaded from the named shop site and returns matching excerpts with URLs. That is far more informative than the bare name 'search'. It does not, however, differentiate itself from the sibling tool 'search_pages', which an agent could easily confuse with this one.

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 explicit when-to-use guidance ('when asked about this shop, use this first'), defines the searchable scope (loaded pages only, not the open web, not post-load updates), and prescribes a fallback workflow: rephrase with synonyms or expanded abbreviations, then read candidate pages, then report not-found rather than guessing. The only gap is that it never names or excludes the sibling 'search_pages' as an alternative.

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