Skip to main content
Glama
Sign In
@growi/mcp-server

@growi/mcp-server

Official
by growilabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getPage

Read-onlyIdempotent

Retrieve the content and metadata of a specific GROWI page using its path or page ID.

Instructions

Get page data about the specific GROWI page

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": "getPage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath of the GROWI page
pageIdNoID of the GROWI page
appNameNoGROWI app name to operate on (optional, uses default if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint, idempotentHint, and openWorldHint, so the description adds little beyond confirming data retrieval. It does not elaborate on pagination, error handling, or behavioral traits not covered by annotations. No contradictions.

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 a single short sentence with no unnecessary words. It is efficient and front-loaded, meeting the need for conciseness.

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?

Given the absence of an output schema, the description does not clarify what 'page data' includes (e.g., content, metadata). The tool is simple, but with many sibling tools, more detail would help distinguish. Annotations and schema are rich, but completeness is moderate.

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

Parameters3/5

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

Schema coverage is 100% with clear parameter descriptions for pageId, path, and appName. The description adds no further meaning beyond 'page data', which is generic. Baseline 3 applies since schema does the heavy lifting.

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 clearly states 'Get page data about the specific GROWI page', which identifies the verb and resource. However, it does not distinguish from sibling tools like 'getPageInfo', which might overlap, so it lacks specificity to differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

No explicit guidance on when to use this tool over alternatives. The description is minimal and does not mention prerequisites or context where this tool is suitable. Implicitly, it is for retrieving page data, but no exclusions or comparisons are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools