Skip to main content
Glama

株式会社グローニティ

ページの中身を読む

fetch
Read-only

「株式会社グローニティ」(grownity.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?

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. Beyond those annotations, the description adds that the tool returns the entire body text and that it is scoped to a single domain; it does not discuss truncation, auth, or rate limits.

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 short sentences with the resource and domain front-loaded, followed by parameter guidance and the accuracy caveat. The id explanation duplicates the schema, so there is minor redundancy.

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 the description does not need to explain return values, and the annotations cover the safety profile. The description adds domain scope and an accuracy-driven usage rule, which leaves no material gap for a single-parameter read tool.

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%, and the schema already explains that id accepts a search-result id, a URL, or a path, including Japanese paths. The description restates that, so it adds little meaning beyond the structured field, which makes the baseline score of 3 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 states a specific verb and resource: it returns the full body text of a loaded page on grownity.co.jp. It is clear what the tool retrieves, but it does not explicitly differentiate itself from the sibling get_page, so an agent must infer the distinction from the returned content rather than from a direct comparison.

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 trigger for use: before answering questions about pricing, dates, conditions, or terms, verify the page body with this. It does not name an alternative or say when not to use it, which keeps it short of a 5.

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