Skip to main content
Glama

株式会社グローニティ

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

get_page
Read-only

「株式会社グローニティ」(grownity.co.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。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

A3.9/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 a closed/site-scoped world, so the safety profile is covered. The description adds genuinely new behavioral context: this is a deprecated legacy alias and its return format differs from fetch. It does not say how the format differs, so it stops at a 3.

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 deprecation notice and the fetch redirect both up front. The company-name parenthetical is slightly heavy but it identifies the scope of the legacy tool, so it largely earns its place.

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?

For a one-parameter, non-destructive read tool with annotations and no output schema, the description covers what an agent needs: it is legacy, what it does, and what to use instead. The only missing piece is the nature of the differing return shape, which matters less for a tool being steered away from.

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?

The schema documents the single url parameter at 100% coverage, including that Japanese paths are acceptable, so the description does not need to explain it. Nothing in the description adds meaning beyond the schema, making baseline 3 correct.

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 the resource and action: it returns the page body, like fetch but in a different shape, and identifies itself as the legacy-name version of the functionality. An agent can tell it apart from fetch by the return format. It never says plainly 'reads a web page' in one front-loaded clause, so it falls just short of a 5.

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?

Explicit guidance is given: use fetch for new work, this remains only for already-connected callers. That names the alternative and the condition that selects it, which is exactly what usage guidance should do.

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