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

@growi/mcp-server

Official
by growilabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

searchPages

Read-onlyIdempotent

Search pages in your GROWI wiki using Elasticsearch queries. Specify path, limit, and offset to refine results.

Instructions

Search pages in GROWI using Elasticsearch

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": {
      "q": "<q>"
    },
    "name": "searchPages"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
pathNo
limitNo
offsetNo
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

C2.3/5.0
Behavior2/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds no extra behavioral context beyond mentioning Elasticsearch.

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

Conciseness2/5

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

The description is very concise but too terse; it lacks essential detail about the tool's parameters and usage, making it insufficiently informative.

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

Completeness1/5

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

With 5 parameters and no output schema, the description is far from complete. It fails to explain search behavior, filtering, or expected return values.

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

Parameters1/5

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

Schema description coverage is only 20%, and the description does not explain the purpose of parameters like q, path, offset, or limit. No additional semantics provided.

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 the tool searches pages using Elasticsearch, which is a specific verb and resource. It distinguishes from siblings like getPage and searchTags by mentioning full-text search via Elasticsearch, though it doesn't explicitly differentiate.

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 versus alternatives such as getPage or searchTags. The description lacks context for optimal use.

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