knowledge-gateway-mcp

Search for a skill

search_skills

Read-onlyIdempotent

Find relevant skills by searching your local library. Get matched candidates for a task, then load one to access the guidance.

Instructions

Search within local library of skills. Returns relevant candidates; it cannot list the complete skill catalog. Call load_skill for a relevant match.

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_skills"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of distinct skill candidates to return.
`query`	Yes	Describe the user's task and the specialized guidance needed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already convey readOnly, idempotent, and non-destructive behavior, so the description does not need to restate those. It adds valuable behavioral context by explaining that the tool returns relevant candidates and explicitly cannot list the complete skill library, which is information not present in annotations or schema.

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 sentences, each earning its place: what the tool does, a key limitation, and the routing to the sibling tool. No filler or redundancy.

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

Completeness5/5

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

For a simple search tool with fully documented parameters, strong annotations, and one clearly identified sibling, the description covers what the tool does, its limitation, and the next step. Nothing essential is missing.

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 description coverage is 100%, so both parameters are already documented meaningfully in the schema. The description does not add parameter-level detail, but it does not need to; the schema carries the semantic load. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'Search within local library of skills.' It clearly distinguishes itself from the sibling load_skill by noting it returns candidates and cannot list the complete catalog, so an agent can tell search apart from load without opening schemas.

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

Usage Guidelines5/5

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

It explicitly directs the agent to 'Call load_skill for a relevant match,' establishing when to use this tool versus the sibling. The limitation statement also clarifies that search is not for enumerating the full catalog, which prevents misuse.

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

Deploy Server