get_source_setupFetch one source's settings and the AWS SES wiring details for it: webhook URL for the SNS subscription, suggested configuration set and topic names, and the remaining setup steps. Use this to finish or verify SES setup for an existing source.
| Name | Required | Description | Default |
|---|---|---|---|
| source_id | Yes | Source id from list_sources |
| Name | Required | Description | Default |
|---|---|---|---|
| setup | Yes | ||
| source | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / setup / properties / aws_region / descriptionPrevious value: -"SES region chosen on the Setup page; null until picked"New value: +"SES region, chosen on the Setup page or inferred from the confirmed SNS topic; null until then"Output schema / properties / setup / properties / launch_stack_url / descriptionPrevious value: -"CloudFormation quick-create link that provisions everything in the user's AWS account; null until a region is picked"New value: +"CloudFormation quick-create link that provisions everything in the user's AWS account; opens the console's last-used region until aws_region is set"Output schema / properties / setup / properties / launch_stack_url / typePrevious value: -[
- "string",
- "null"
-]New value: +"string"Output schema / properties / setup / properties / aws_regionAdded value: +{
+ "description": "SES region chosen on the Setup page; null until picked",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / setup / properties / launch_stack_urlAdded value: +{
+ "description": "CloudFormation quick-create link that provisions everything in the user's AWS account; null until a region is picked",
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / setup / requiredPrevious value: -[
- "webhook_url",
- "config_set_name",
- "sns_topic_name",
- "setup_url",
- "steps"
-]New value: +[
+ "webhook_url",
+ "config_set_name",
+ "sns_topic_name",
+ "aws_region",
+ "launch_stack_url",
+ "setup_url",
+ "steps"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only that the read is scoped to 'one source' and geared toward finishing/verifying setup; it discloses no auth requirements, rate limits, or side effects beyond what the annotations state.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no filler: the first front-loads the returned payload and the second states the use case. Every clause carries information an agent needs to select the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need not be explained, yet the description helpfully previews them; annotations cover the safety profile and the sole parameter is documented. The only minor gap is the absence of any note about permissions or whether the source must be in a particular setup state for meaningful results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single parameter source_id is documented as 'Source id from list_sources.' The description refers to 'one source's settings' but adds no naming, format, or sourcing detail beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Fetch) and resource (one source's settings / AWS SES wiring) and enumerates the concrete payload: webhook URL for the SNS subscription, suggested configuration set and topic names, and remaining setup steps. This payload profile is unique among the siblings (list_sources, create_source, update_source, get_message, email_stats, search_events), so an agent can distinguish it without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly frames the use case: 'Use this to finish or verify SES setup for an existing source,' which also implicitly excludes creating a source (create_source) or listing them (list_sources). There is no explicit when-not statement or named alternative tool, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.