Skip to main content
Glama

ページの中身を読む

fetch
Read-only

「shikake101.co.jp」(shikake101.co.jp)の、読み込んだページの本文を全文返します。id には、探した結果の id(ページの URL)か、ページの 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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes探した結果の id(ページの URL)。ページの URL かパスでも可(日本語のままでも可)

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, and an output schema exists. The description adds the useful detail that it returns the FULL body text (as opposed to an excerpt) and that it is confined to shikake101.co.jp. It does not mention truncation, fetch failures, or what happens with an invalid path, so it adds only moderate 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?

Three sentences, front-loaded with what is returned, then how to pass the id, then when to use it. The only waste is repeating the domain name parenthetically at the start, which adds no information.

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 one required parameter, full schema coverage, annotations, and an output schema, the description covers purpose, accepted input forms, and the accuracy-driven use case. Nothing essential for a correct invocation is missing, though a note on domain restriction behavior or failure modes would round it out.

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 id parameter is already documented as a page URL or path, including that Japanese is acceptable. The description restates the same accepted forms (id from search results, URL, or path), so it adds little beyond the schema, which fits the baseline of 3.

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 returns the full body text of a loaded page on shikake101.co.jp. That is clear enough to distinguish it from a search or list operation, but it never names a sibling such as get_page or search_pages, so the agent has to infer the boundary from the '探した結果の id' phrasing.

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 a concrete use condition: for anything where accuracy matters (fees, dates, conditions, terms), verify the body text before answering. That is a clear positive trigger, but there is no explicit when-not guidance and no named alternative for cases where a summary or listing suffices.

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