Skip to main content
Glama

search_kb

Read-onlyIdempotent

Search the MSP knowledge base for procedures and policies, returning ranked excerpts with article IDs and sections for accurate citation.

Instructions

Search the Summit Managed IT knowledge base for procedure and policy.

Returns ranked excerpts with the article ID and section that produced each one, so any fact you use can be cited. The knowledge base is the only authoritative source of Summit procedure: reset URLs, SLA timeframes, approval requirements, escalation paths.

Query with the words the KB itself would use — symptoms and nouns ("account lockout", "vpn certificate", "mailbox full"). Long natural-language sentences score worse than three or four content words, because matching is keyword overlap, not semantic similarity.

WHAT IT DOES NOT DO

  • Does not search tickets. For customer requests use search_tickets.

  • Does not write replies. For a reply grounded in these articles, use draft_response, which performs its own retrieval and returns the grounding alongside the draft.

  • Does not paraphrase or summarise. Excerpts are returned verbatim so that timeframes, URLs, and limits survive intact. Reproduce them exactly; do not round "15 minutes" or invent a support phone number. The corpus contains no phone numbers at all.

ERRORS KB_NO_MATCH — nothing scored above threshold. Retry once with broader or different content words. If it still misses, the knowledge base does not cover the topic: say so plainly rather than answering from general knowledge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
queryYes
messageNo
excerptsNo
error_codeNo
Behavior5/5

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

Discloses that excerpts are returned verbatim without summarization, enabling citation. Annotations already indicate readOnly and idempotent; description adds retrieval behavior and error context.

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

Conciseness4/5

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

Well-structured with clear sections, front-loaded purpose, and minimal redundancy. Slightly long but every sentence adds value.

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?

Covers purpose, query strategy, not-do list, error handling, and output format. Sufficient for an agent to select and use correctly, especially given output schema exists.

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 0%, but description explains how to formulate queries (using content words) and implies that limit and category are optional. However, no explicit parameter descriptions are given.

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 clearly states it searches the knowledge base for procedure/policy, returns ranked excerpts, and distinguishes itself from sibling tools like search_tickets and draft_response.

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?

Provides explicit guidance on when to use (for procedures/policies), how to query (use keywords not sentences), what it does not do, and error handling (KB_NO_MATCH).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jackson-DM/msp-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server