Skip to main content
Glama
Sign In
cognigy-ai-mcp-management-server

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

update_knowledge_store

Idempotent

Modify a Cognigy.AI knowledge store's name or description. Dry run validates; set dryRun=false to commit the update.

Instructions

Updates an existing Cognigy.AI knowledge store. Use this to change name or description. MUTATING: Set dryRun=false to update.

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": {
      "knowledgeStoreId": "<knowledgeStoreId>"
    },
    "name": "update_knowledge_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the knowledge store
dryRunNoIf true (default), validates without updating. Set to false to actually update.
descriptionNoNew description
knowledgeStoreIdYesThe knowledge store ID to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.2/5.0
Behavior4/5

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

Adds context that dryRun=false is needed to actually update, complementing annotations (readOnlyHint=false, idempotentHint=true). No contradiction.

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?

Two sentences, front-loaded with purpose, no unnecessary words.

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?

For a simple update tool, the description is adequate. Could mention return value, but not required given schema and annotations.

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 covers 100% of parameters with descriptions. The description reiterates name and description but adds no new info beyond the 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?

The description clearly states it updates an existing knowledge store and specifies the fields (name/description). It distinguishes itself from sibling tools like create_knowledge_store and delete_knowledge_store.

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?

Explicitly says 'Use this to change name or description' and warns about dryRun. Could mention not to use it for deletion, but the purpose is clear enough.

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