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

cognigy-ai-mcp-management-server

by TsvetanG2
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript

get_flow_settings

Read-onlyIdempotent

Retrieve NLU settings, thresholds, and flow-level configurations for a Cognigy.AI flow to review before making updates.

Instructions

Gets the settings/configuration of a Cognigy.AI flow. Returns NLU settings, thresholds, and other flow-level configurations. Use this before updating flow settings.

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": {
      "flowId": "<flowId>"
    },
    "name": "get_flow_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowIdYesThe flow ID to retrieve settings for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety traits. The description adds context about returned content (NLU settings, thresholds) and recommends usage before updates, but doesn't reveal additional behavioral nuances.

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, zero waste. Front-loaded with the main action, immediately followed by return overview and usage hint.

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?

Provides enough information for an agent to understand what the tool returns and when to use it. No output schema exists, but the high-level return description suffices for a simple read tool.

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 clear description for flowId. Description adds no further parameter detail, meeting the baseline for high schema coverage.

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?

Clearly states 'gets the settings/configuration' of a flow, specifying the resource precisely. Differentiates from siblings like 'get_flow' which likely retrieves structure, not settings.

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 advises 'Use this before updating flow settings', providing a clear context for tool usage. Though no explicit alternatives are named, the guidance is direct and helpful.

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