@growi/mcp-server

Official

by growilabs

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

getRevision

Read-onlyIdempotent

Retrieve detailed information about a specific revision in a GROWI wiki by providing the revision ID and page ID.

Instructions

Get detailed information about a specific revision in GROWI

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": {
      "id": "<id>",
      "pageId": "<pageId>"
    },
    "name": "getRevision"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Revision ID to get details for
`pageId`	Yes	Page ID that the revision belongs to
`appName`	No	GROWI app name to operate on (optional, uses default if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1May 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, etc. Description adds minimal context about 'detailed information' but no behavioral details like error handling or required permissions.

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?

Single sentence, front-loaded, no unnecessary words. Efficient and clear.

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

Completeness2/5

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

No output schema, but description fails to explain what 'detailed information' includes or the response format. For a single-revision query, more context is needed.

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 has 100% coverage with descriptions for all parameters. Description does not add any parameter info beyond the schema, so baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states getting detailed info about a specific revision in GROWI, with explicit verb and resource. Distinguishes from sibling listRevisions which lists multiple.

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

Usage Guidelines2/5

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

No guidance on when to use this tool over alternatives like listRevisions or getPage. Does not mention prerequisites or context.

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