Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_ses_list_identities

Retrieve verified email addresses and domains from AWS SES to manage email sending permissions and monitor authentication status.

Instructions

List SES verified identities (email addresses and domains).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aws_ses_list_identities"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')
identity_typeNoFilter by identity type (optional)
max_itemsNoMaximum number of identities to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentioning 'verified identities' adds valuable SES-specific context (only verified identities are returned), but lacks confirmation that this is read-only, doesn't describe pagination behavior despite 'max_items' parameter, and omits output format details.

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?

Single sentence, front-loaded with specific action and resource. Efficient and waste-free, though given zero annotations and no output schema, slightly more behavioral context could have been added without sacrificing clarity.

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

Completeness3/5

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

Minimal but adequate for a simple list operation with complete schema coverage. Lacks output description (pagination tokens, identity ARN format) and AWS-specific behavioral notes (rate limiting, eventual consistency), but the 100% parameter schema coverage mitigates some gaps.

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%, establishing baseline of 3. Parenthetical '(email addresses and domains)' implicitly maps to the identity_type enum values, but description does not explicitly document parameter usage, constraints, or interdependencies beyond what the schema already provides.

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?

Clear verb ('List') and resource ('SES verified identities') with specific scope (email addresses and domains). Distinguishes from siblings like aws_ses_send_email and aws_ses_get_identity_verification_attributes by focusing on enumeration rather than action or attribute retrieval, though it doesn't explicitly contrast with them.

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 on when to use this versus alternatives (e.g., aws_ses_get_identity_verification_attributes for checking status of specific identities). No mention of prerequisites like AWS credentials or when filtering by identity_type is recommended.

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