Skip to main content
Glama

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

list_pages
Read-only

「shikake101.co.jp」(shikake101.co.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/5.0
Behavior4/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, but the description still adds value: it discloses the result shape (title + URL), the page size of 50, the limit ceiling of 200 and the offset-based continuation. It does not state ordering or whether a total count is returned, which is the remaining gap.

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 return shape before pagination and usage. The only waste is the redundant repetition of the domain name in parentheses right at the start.

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 two-parameter listing tool with annotations covering the safety profile and no output schema, the description supplies scope, return fields, pagination mechanics and when-to-use. Only ordering, total count and the explicit link to the sibling search tool are 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 carries the burden and largely meets it: limit is explained as page size with a maximum of 200, and offset as the way to fetch the next page. The default of 50 is restated, though no guidance is given on sensible offset values or whether offset must be a multiple of limit.

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 uses a specific verb and resource — it returns the list of pages loaded on shikake101.co.jp with their titles and URLs — so the agent knows exactly what comes back. It gestures at the search alternative ("when you can't find something by searching") but never names search_pages, so sibling differentiation is only implicit.

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?

Two concrete usage conditions are given: when you want to know what pages exist, and when a search has failed to surface something. That is real routing guidance, but the fallback condition does not name the sibling tool it contrasts with, leaving the agent to infer that search_pages is the alternative.

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