Skip to main content
Glama
Sign In
Anam MCP Server

Anam MCP Server

Official
by anam-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_knowledge_tool

Create a searchable knowledge tool for retrieving documents. Integrates selected knowledge folders into a custom tool for RAG-based document search.

Instructions

Create a knowledge tool for RAG (document search).

Args: name: Tool name in snake_case (e.g., "search_product_docs") description: When the LLM should use this tool folder_ids: List of knowledge folder UUIDs to search

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": {
      "name": "<name>",
      "description": "<description>",
      "folder_ids": "<folder_ids>"
    },
    "name": "create_knowledge_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
descriptionYes
folder_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states 'create' without detailing side effects, required permissions, idempotency, or uniqueness constraints. For a creation tool, more context is needed to avoid misuse.

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?

The description is short and front-loaded with the purpose, followed by a compact arg list. Every sentence serves a purpose, though structuring the args more formally could improve readability.

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

Completeness3/5

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

For a creation tool with no annotations and an output schema, the description covers the core inputs but omits return value details, limits, or potential errors. It is adequate but leaves gaps for an agent.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must explain parameters. It does so: name format (snake_case), description purpose (when to use), and folder_ids (list of UUIDs). This meaningfully augments the schema's bare types.

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 'Create a knowledge tool for RAG (document search),' specifying the verb (create) and resource (knowledge tool) with its purpose (RAG/document search). This distinguishes it from sibling tools like create_webhook_tool or create_llm.

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

Usage Guidelines3/5

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

The description includes a note on the 'description' parameter ('When the LLM should use this tool'), which provides implicit guidance on when the resulting tool will be used, but lacks explicit instructions on when to use this creation tool versus alternatives (e.g., update_tool) or prerequisites (e.g., needing existing knowledge folders).

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

Deploy Server

Other Tools