Skip to main content
Glama

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

ページの中身を読む(以前の名前)

get_page
Read-only

「ぎんざ姿オンラインショップー極上の天然とらふぐと近江牛の味」(shop.ginzasugata.online)の以前の名前の機能です(すでにつないでいる人のために残しています)。fetch と同じようにページの本文を返しますが、返す形が違います。新しく使うときは fetch を使ってください。

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": {
      "url": "<url>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesページの URL かパス(日本語のままでも可)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond the annotations by disclosing that the returned shape differs from fetch, though it does not say how it differs or mention any rate/permission constraints.

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?

Three sentences with the legacy status and the applicable site front-loaded, followed by the fetch comparison and the redirect instruction. Efficient, though slightly repetitive in restating the legacy framing.

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 no output schema and annotations covering safety, the only real remaining gap is the unspecified difference in return format, which the description flags but does not characterize. For a deprecated read-only tool with a trivial one-param schema, this is close to complete.

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 description coverage is 100% and the single url parameter is fully documented in the schema, including tolerating Japanese characters. The description adds no parameter semantics beyond that, so the baseline 3 applies.

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?

The description states a specific verb and resource (returns the page body) and immediately frames the tool as a legacy alias of fetch, distinguishing it from that sibling without the agent needing to open either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly tells the agent when NOT to use this tool ('新しく使うときは fetch を使ってください') and why it still exists (kept for already-connected users), which is exactly the routing guidance needed for a deprecated 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