Skip to main content
Glama
TsvetanG2

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

update_function

Idempotent

Modify an existing Cognigy.AI function's name, code, or enabled state. Set dryRun=false to apply changes; by default, it validates.

Instructions

Updates an existing Cognigy.AI Function. Use this to change its name or code, or to enable/disable it. MUTATING: Set dryRun=false to update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoUpdated function code
nameNoNew name for the function
dryRunNoIf true (default), validates without updating. Set to false to actually update.
functionIdYesThe function ID to update
isDisabledNoDisable (true) or enable (false) the function

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • removedInput schema / properties / description
      Removed value: -{
-  "description": "New description",
-  "type": "string"
-}
    • addedInput schema / properties / isDisabled
      Added value: +{
+  "description": "Disable (true) or enable (false) the function",
+  "type": "boolean"
+}
    • removedInput schema / properties / parameters
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Updated parameters schema",
-  "propertyNames": {
-    "type": "string"
-  },
-  "type": "object"
-}
  2. First observedv0.1.4

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false; the description usefully reinforces the mutating nature and warns that the default dryRun=true will not persist changes. It stops short of describing permissions, validation behavior, or what a dry-run returns.

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?

Three short sentences, front-loaded with the action and the field list, then the mutation caveat. No filler.

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 five-parameter mutation tool with no output schema, the description covers purpose, target fields, and the dry-run pitfall. It could add failure/auth context, but nothing critical for correct invocation is missing given the rich schema.

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 description coverage is 100%, so all five parameters including dryRun and isDisabled are already documented in the schema. The description mostly restates that dryRun must be false to persist, adding marginal value beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb+resource ('Updates an existing Cognigy.AI Function') and enumerates the mutable fields (name, code, enable/disable). This clearly distinguishes it from create_function and delete_function among the siblings.

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?

Gives clear usage context ('use this to change its name or code, or to enable/disable it') and a critical operational instruction to set dryRun=false. It does not explicitly name alternatives like create_function/delete_function, but the CRUD framing makes the boundary evident.

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