Skip to main content
Glama

search_wiki

Search the gknowledge wiki to find matching pages by query and view slug, page type, and a one-line summary; use read_page for full details.

Instructions

Search the gknowledge wiki. Returns matching pages with slug, type and a one-line summary. Use read_page for details.

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": {
      "query": "<query>"
    },
    "name": "search_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to look for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden alone. It usefully discloses the return shape and implies a read-only lookup, but says nothing about permissions, result caps for the limit parameter, or whether matches are keyword or full-text.

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 short, front-loaded sentences with zero filler: purpose, return contract, and the handoff to read_page. Nothing would be lost by keeping it exactly as is.

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?

There is no output schema, so the description earnestly covers return fields, which is the right call for a small two-parameter tool. The remaining gap is the undocumented 'limit' semantics, which an agent needs in order to page or size results correctly.

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

Parameters2/5

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

Schema coverage is only 50%: 'query' has a terse description ('Words to look for') while 'limit' is documented only by its default of 8, with no stated maximum or meaning. The description does not compensate for that gap, adding no explanation of matching rules or what limit bounds.

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?

States a specific verb and resource ('Search the gknowledge wiki') and adds the return shape (slug, type, one-line summary), which tells an agent exactly what this yields versus read_page. It stops short of specifying which fields are searched or how matching works, so it is clear but not maximally specific.

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?

Explicitly names the alternative 'read_page' and the condition selecting it ('for details'), giving the agent a clean two-step search-then-read pattern. It offers no guidance relative to other siblings like list_pages or ask, so the routing guidance is real but partial.

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