Skip to main content
Glama
@yawlabs/aws-mcp

@yawlabs/aws-mcp

Official
by YawLabs

aws_login_complete

Blocks until the AWS SSO browser login started by aws_login_start finishes, then returns the verified identity, token status, or a structured error.

Instructions

Block until the SSO login started by aws_login_start finishes (user completed auth in browser, or subprocess exited with error). Returns the new identity on success, or a structured error. For an ssoSession login there is no profile yet, so it returns the token status and points to aws_sso_list_assignments instead of an identity.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "aws_login_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoRegion for the post-login identity check.
profileNoProfile to verify identity against after login. Defaults to $AWS_PROFILE or 'default'.
sessionIdYesThe sessionId returned by aws_login_start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true but say nothing about blocking semantics. The description adds genuinely useful context: this call blocks on human browser interaction or subprocess exit, returns identity on success or a structured error, and returns a different shape (token status) for ssoSession logins. The one notable omission is that blocking duration/timeout behavior is never stated.

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?

Three sentences, front-loaded with the blocking behavior and the sibling dependency, with no filler. The final sentence is dense but each clause carries distinct information about the ssoSession return path.

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?

There is no output schema, so the description carries the return-value burden, and it does describe both the identity-on-success and structured-error outcomes plus the ssoSession variant. Completeness would be higher if it described what the structured error looks like or what happens if the wait never resolves.

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%, so sessionId, region, and profile are already documented in the schema. The description restates only that sessionId comes from aws_login_start (also in the schema) and says nothing about region or profile, so it adds essentially nothing beyond structured data. Baseline 3 applies.

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?

States a specific verb and resource ('Block until the SSO login started by aws_login_start finishes') and makes the pairing with aws_login_start explicit, so an agent can tell it apart from the start/session siblings immediately. It also carves out the ssoSession case, which is a real behavioral distinction.

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?

Usage context is clear: call this after aws_login_start to await completion, and for ssoSession logins follow the returned pointer to aws_sso_list_assignments. It does not state exclusions or timing expectations (no timeout, no guidance on what to do if the user never completes auth), which keeps it below a 5.

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