Skip to main content
Glama

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

サイトの概要を知る

site_overview
Read-only

「ぎんざ姿オンラインショップー極上の天然とらふぐと近江牛の味」(shop.ginzasugata.online)がどんなサイトかを返します。種類・紹介文・読み込んだページ数・主なページが分かります。最初にサイトの全体像をつかみたいときに使います。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "site_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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. The description adds real value beyond that by disclosing the shape of the response (type, summary text, page count, main pages) and implying it targets one fixed site, which is useful since no output schema exists. It does not mention limits, pagination, or caching, keeping it short of a 5.

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 compact sentences: the first front-loads what is returned, the second gives the triggering condition. Every clause earns its place with no redundancy or filler.

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?

With no parameters, no nested objects, and no output schema, the description carries the burden of explaining the return shape and does so (type, description, page count, main pages). Annotations cover safety, so nothing an agent needs to invoke this correctly is missing.

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?

The tool takes zero parameters (empty schema, 100% coverage trivially), so there is nothing for the description to clarify or compensate for. Baseline 4 applies; no param-related content is required or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('returns what kind of site X is') and enumerates the return payload: type, description, number of pages loaded, and main pages. The phrase '最初にサイトの全体像をつかみたいとき' implicitly separates it from per-page siblings like get_page and list_pages, which an agent can use to route correctly.

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?

Explicitly states the situation to use it in ('when you first want to grasp the overall picture of the site'), which is genuine directional guidance. However, it never names a sibling tool or states when NOT to use it (e.g., 'use get_page for a single page'), so it falls short of full when/when-not/alternatives coverage.

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