Skip to main content
Glama
Sign In
Amazon Connect MCP Server

Amazon Connect MCP Server

by mundurragacl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

analytics_list_contact_evaluations

List all evaluations for a specific contact by entering the contact ID and instance ID, enabling quick access to performance reviews and quality assessments.

Instructions

List evaluations for a contact.

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_id": "<contact_id>"
    },
    "name": "analytics_list_contact_evaluations"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYes
instance_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 carry the full behavioral burden. It only says 'List evaluations for a contact' without disclosing sorting, filtering, pagination, or the need for an instance_id context.

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 a single short sentence, which is concise and front-loaded with the verb. However, it is so minimal that it borders on under-specification, though not as extreme as a tautology.

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?

Given two required parameters and no annotations, the description is too sparse to be contextually complete. It does not explain the role of instance_id, what counts as an evaluation, or when this tool is appropriate.

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

Parameters2/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 compensate. It provides a vague hint about contact_id via 'for a contact', but gives no explanation of instance_id or how the parameters interact.

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 the tool lists evaluations for a contact, using a specific verb and resource. It distinguishes from sibling tools like analytics_list_evaluation_forms, which lists forms, and analytics_start_contact_evaluation, which starts an evaluation.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or related analytics tools.

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