knowledge-base-mcp

search

Retrieve knowledge base documents by matching selected terms and labels, using AND/OR operators to refine results.

Instructions

Search the knowledge base by free-text terms and/or labels.

    Args:
        terms: Words/phrases to partial-match against title and content.
        term_operator: "AND" requires every term to match, "OR" requires any one to match.
        labels: Labels to filter on.
        label_operator: "AND" requires every label, "OR" requires any one label.
        limit: Maximum number of results to return.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`terms`	No
`labels`	No
`term_operator`	No	AND
`label_operator`	No	AND

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Describes partial matching behavior and operator logic. No annotations exist, so description carries full burden. Could add more about result ordering or error handling, but covers core behaviors.

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?

Concise docstring format with clear Args section. Every sentence adds value with no 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?

Given 5 parameters (0 required), output schema exists, the description covers all parameter semantics and search logic. Output details are handled by output schema, so no further explanation needed.

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

Parameters5/5

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

With 0% schema description coverage, the description fully explains each parameter: terms are partial-matched, operators control matching logic, labels filter, limit caps results. Adds significant meaning beyond bare schema.

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 'Search the knowledge base by free-text terms and/or labels' using a specific verb and resource. Distinguishes from sibling tool 'add_document' by its search functionality.

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?

Provides detailed usage for each parameter including operators and limit. Implicitly distinguishes from add_document but lacks explicit when-to-use or when-not-to-use guidance.

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

Deploy Server