Skip to main content
Glama

pare-suitengumae.jp

どんなページがあるか見る

list_pages
Read-only

「pare-suitengumae.jp」(pare-suitengumae.jp)で読み込んだページの一覧を、タイトルと URL で返します。一度に 50 件ずつ(limit で最大 200 件)で、続きは offset で取れます。どんなページがあるか知りたいときや、探しても見つからないときに使います。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, non-open-world operation. The description adds useful behavior beyond that by explaining pagination: 50 items at a time, limit up to 200, and continuation via offset, plus the returned fields of title and URL.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it first states what is returned, then explains pagination, then gives the usage situation. Every sentence adds concrete information without repetition.

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

Completeness5/5

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

For a simple read-only list tool with two optional parameters and no output schema, the description covers the essential return content, pagination behavior, and when to use it. Nothing critical for correct invocation is missing.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does: limit controls page size up to 200 and defaults to 50 per batch, while offset retrieves subsequent pages. It does not elaborate on edge cases such as offsets beyond the available results, but the core semantics are covered.

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 a list of pages loaded from pare-suitengumae.jp with titles and URLs. It does not explicitly name a sibling such as search_pages, but the phrase about using it when searching fails implicitly distinguishes it from search-oriented tools.

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 clear usage context: use it when you want to know what pages exist or when a search does not find what you need. It does not state explicit exclusions or name the alternative search tool directly, but the intended situation is clear.

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