Amazon Connect MCP Server

config_describe_contact_flow

Retrieve detailed information about a specific Amazon Connect contact flow by providing the instance ID and contact flow ID. This action returns configuration details needed to inspect or manage your contact center flows.

Instructions

Get contact flow details.

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": {
      "instance_id": "<instance_id>",
      "contact_flow_id": "<contact_flow_id>"
    },
    "name": "config_describe_contact_flow"
  }
}

Input Schema

Name	Required	Description	Default
`region`	No
`instance_id`	Yes
`contact_flow_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are present, and the description only restates the action without revealing behavioral traits such as read-only nature, permissions, or response characteristics. 'Get contact flow details' adds little beyond the tool name.

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 extremely short and front-loaded, but it is under-specified rather than efficiently concise. It captures the core purpose but omits essential context, balancing brevity with inadequacy.

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

Completeness2/5

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

With no annotations, zero parameter documentation, and only a terse statement, the description is insufficient for a tool with three parameters and an output schema. The output schema exists, but the description does not help the agent understand when or how to invoke the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention any parameters. Although parameter names like instance_id and contact_flow_id are somewhat self-explanatory, the description provides no additional context or detail about them.

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 uses a specific verb ('Get') and resource ('contact flow details'), clearly indicating a describe operation. It distinguishes from sibling tools like config_list_contact_flows and config_create_contact_flow, but does not elaborate on what 'details' includes.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives such as config_list_contact_flows or config_describe_queue. There is no mention of prerequisites, use cases, or exclusions.

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

Deploy Server