Skip to main content
Glama

株式会社グローニティ

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

list_pages
Read-only

「株式会社グローニティ」(grownity.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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral detail: 50 items per page by default, a limit ceiling of 200, and offset-based continuation — the kind of pagination context an agent needs before calling. It does not say whether a total count or ordering is returned, but with no output schema that is a minor omission.

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?

Three compact sentences: scope and return fields first, then pagination mechanics, then usage triggers. Nothing is repeated and every clause carries information the agent needs.

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, no-output-schema listing tool this covers the essentials — data scope, returned fields, page size, and continuation strategy. Missing only secondary details such as result ordering and whether truncation/total is signalled.

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 the parameter meaning, and it largely does: limit is bounded at 200 with a default of 50, and offset is described as the way to fetch the continuation. The only gap is that offset's unit/relationship to limit (i.e., advance by page size) is left implicit.

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 — returns a list of pages with their titles and URLs — and scopes it to one site (grownity.co.jp). It is clear what the tool produces, though differentiation from siblings like search_pages is only implied through the 'when you can't find it by searching' clause rather than stated explicitly.

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 two concrete triggers: when you want to know what pages exist, and when searching fails to surface something. That implicitly positions listing as a fallback to search, which is useful routing guidance, but it never names the alternative tool or states exclusions (e.g., no filtering by keyword).

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