Skip to main content
Glama
esurovtsev

KnowFlow MCP

by esurovtsev

search_knowledge

Retrieve information from a knowledge base by searching with a query. Get relevant content snippets, source filenames, and relevance scores to answer questions accurately.

Instructions

Searches for information in the knowledge base. Use this tool when you need to retrieve specific information or context.

Available knowledge sources:
    - docs: For architecture documents, technical specifications, and notes

IMPORTANT USAGE INSTRUCTIONS:
  1. This tool returns content snippets directly from the knowledge base
  2. DO NOT attempt to access or load the source files mentioned in metadata
  3. Use ONLY the content field from each result to answer queries
  4. ALWAYS cite the EXACT source filenames (including .md extension) when presenting information to users (e.g., 'According to architecture-notes.md...')
  5. Source filenames help users understand where information comes from and allow them to verify it if needed
  6. The lastModified field indicates when the information was updated - newer information may be more relevant
  7. The score field (0-1) indicates how relevant the result is to the query - higher values are more relevant
  8. All necessary information is contained in the content snippets

Response format:
{
  instructions: "How to use these results",
  results: [
    {
      content: "The actual text snippet to use (FOCUS ON THIS)",
      metadata: {
        reference: "Filename for reference only - DO NOT ATTEMPT TO LOAD",
        source: "docs",
        lastModified: "Date of last modification",
        score: "Relevance score between 0-1"
      }
    }
  ]
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return
queryYesThe search query to find relevant information
sourceNoThe preferred knowledge source to search (e.g., jira, confluence, docs, slack). If specified, results from this source will be prioritized.
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It reveals that the tool returns content snippets, includes metadata fields (score, lastModified), and warns against accessing source files. It implies a read-only operation, though it does not explicitly declare read-only. Overall, it provides good behavioral context.

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

Conciseness3/5

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

The description is verbose, containing a full response format example and multiple usage bullet points. While structured, it could be more concise. Every sentence contributes, but the length may reduce quick comprehension.

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?

With no output schema, the description compensates by providing a detailed response format with explanations of each field (content, metadata, reference, score, etc.). It also covers usage instructions and result interpretation. For a 3-parameter tool, this is fairly complete.

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 100%, so baseline is 3. The description adds some value by listing the 'docs' source and instructing on using score/lastModified, but it does not significantly enhance the schema descriptions for 'query' and 'limit'. The source parameter is somewhat enhanced with an example list, but not enough to raise the score.

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 clearly states 'Searches for information in the knowledge base' and lists an available source ('docs'). This provides a specific verb and resource, but it does not distinguish from potential sibling tools (none provided), and the purpose is somewhat broad.

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?

The description explicitly says 'Use this tool when you need to retrieve specific information or context.' It also provides detailed usage instructions (e.g., 'DO NOT attempt to access or load the source files', 'Use ONLY the content field') that guide the agent on proper use. There are no sibling tools to compare against, but the guidance is clear.

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/esurovtsev/know-flow-mcp'

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