Skip to main content
Glama

Search wikis

wiki_search
Read-only

Full-text search over page content under a path.

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": {
      "path": "<path>",
      "query": "<query>",
      "org": "<org>"
    },
    "name": "wiki_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's path; the name and colon alone (general:) is the whole wiki.
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/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 without the description. The description contributes only the path-scoping trait and says nothing about result ranking, truncation, or whether matches include page titles versus body text only, which are the behaviors an agent would want here.

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?

A single eight-word sentence with zero filler, leading with the operation and immediately following with its scope. Nothing is repeated from the schema or annotations.

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?

For a four-parameter required-heavy search tool with no output schema, the definition covers what is searched and where, but an agent still lacks the mechanics: query syntax, default and maximum result behavior beyond the schema's limit, and the shape of a hit. Adequate at the minimum viable level, with real gaps.

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 50%: org and path are well documented in the schema, while query and limit are not. The description partially compensates by clarifying that the query matches page content and that path bounds the search area, but it says nothing about query syntax (operators, phrase quoting) or what limit controls, so the undocumented half remains thin.

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 gives a specific verb and resource combination ("Full-text search over page content") plus a scoping constraint ("under a path"), which is enough to distinguish it from retrieval siblings like wiki_get or wiki_read. It doesn't name any sibling explicitly, so the differentiation is inferred rather than stated.

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?

There is no guidance on when to use this tool rather than reading a page directly (wiki_read/wiki_get) or browsing the hierarchy (wiki_tree). The phrase "under a path" implies a scope constraint but never states that searching is scoped to a wiki/page subtree, nor when full-text search is preferable to navigation.

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