Skip to main content
Glama

pare-suitengumae.jp

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

search_pages
Read-only

「pare-suitengumae.jp」(pare-suitengumae.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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact, that the return shape differs from `search`, but it never says how it differs, so an agent cannot plan around the output. With annotations carrying the rest, a 3 is appropriate.

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, front-loaded with the legacy/deprecation status and the redirect to `search`. No redundant wording. Slightly repetitive in restating the domain twice, but negligible.

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 legacy alias with annotations and no output schema, the definition covers status, alternative, and the key behavioral delta. The unresolved 'different format' claim and the undocumented `limit` are the remaining gaps an agent would care about.

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` has a description and example, while `limit` has only type/default/min/max and no explanation in either place. The description says nothing about either parameter, so it does not compensate for the uncovered half. It adds no meaning 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?

The description states a specific behavior: it searches within the site like `search` but returns a different shape, and it is a retained former-name/legacy function of pare-suitengumae.jp. It explicitly distinguishes itself from the sibling `search`. It never says what kind of content is searched (pages vs. full site corpus), which keeps it 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 Guidelines4/5

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

It gives explicit routing: for new usage, call `search` instead, and it explains why this tool still exists (existing integrations). That is a clear when-not-to-use signal plus a named alternative. The only gap is that the positive case for calling this tool is left implicit as 'already-connected clients'.

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