Skip to main content
Glama

list_aws_member_accounts

Read-onlyIdempotent

The AWS member accounts Plutus discovered behind the connected organization: how many are readable, unreadable or excluded, and per account the access status, the fix when it is unreadable, and whether it is included. enabled false means multi-account inventory is off for this account. Change inclusion with set_aws_member_account_included. Mirrors GET /api/accounts/:accountId/aws/member-accounts.

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": "list_aws_member_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful semantics beyond that by documenting what each row contains and that `enabled` false means multi-account inventory is disabled for the account. It says nothing about ordering, pagination, or empty-result behavior, so the added context is helpful but partial.

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?

Purpose is front-loaded and every sentence carries information: the enumeration of entry fields, the `enabled` caveat, the mutation pointer, and the endpoint mirror. The middle clause ('how many are readable, unreadable or excluded, and per account...') is densely packed and slightly awkward to parse, but nothing is wasted.

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?

With no output schema, the description correctly carries the burden of describing return content (counts by readability plus per-account status, fix, and inclusion). It leaves implicit which account scope the endpoint resolves to and does not mention paging, so it is solid but not fully self-sufficient for a zero-parameter listing tool.

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

Parameters4/5

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

The tool takes no parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The `enabled` mention refers to a returned field rather than an input, so it neither helps nor hurts this dimension.

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 ('The AWS member accounts Plutus discovered behind the connected organization') plus the shape of each entry: readability counts, per-account access status, remediation, and inclusion flag. This is clearly distinct from the other list_* siblings and mirrors a concrete endpoint, so an agent can pick it without opening the schema.

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?

The definition routes mutation intent explicitly to set_aws_member_account_included, which is the key alternative an agent would otherwise confuse with this read. It does not spell out a when-not-to-use condition (e.g. single-account setups where the list is irrelevant), so it stops short of full explicit guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources