Skip to main content
Glama

株式会社グローニティ

サイトの中を探す(以前の名前)

search_pages
Read-only

「株式会社グローニティ」(grownity.co.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。search と同じようにサイトの中を探しますが、返す形が違います。新しく使うときは search を使ってください。

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": {
      "query": "<query>"
    },
    "name": "search_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes探したい言葉(例: 料金 支払い方法)

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, destructiveHint=false, openWorldHint=false, so safety is covered structurally. The description adds the behavioral fact that the return shape differs from search, but never says what that shape is, leaving the most operationally relevant trait unexplained. Context beyond annotations is present but thin.

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 front-loaded, so an agent reads the most decision-relevant fact first. Mild repetition of the '以前の名前' framing from the title is the only waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only search tool with no output schema, the description covers identity and routing adequately. It is incomplete on the one thing it raises itself — what the differing return shape actually is — and says nothing about the limit parameter, which an agent must still infer from the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: query is documented with examples in the schema, while limit (default 5, max 20) is undocumented anywhere. The description mentions no parameters at all, so it fails to compensate for the coverage gap and adds nothing beyond the schema.

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?

States a specific verb and resource (サイトの中を探す — searches within the site) and explicitly contrasts itself with the sibling search by saying the return shape differs. It also discloses its legacy status, so an agent can identify what it is. Slight vagueness remains about what exactly is searched (pages vs. whole site), but the core purpose is separable from siblings.

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?

Gives explicit routing guidance: this is retained only for people already connected, and new usage should call search instead. That names the alternative and the condition that selects it, which is exactly what an agent needs to avoid picking a deprecated tool.

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