Skip to main content
Glama

AWS Knowledge

by aws.api.global.knowledge-mcp

aws___get_regional_availability

Read-only

AWS resource availability per region.

  • Max 10 regions; multi-region needs filters; single-region supports next_token.

  • Status: isAvailableIn | isNotAvailableIn | isPlannedIn | Not Found.

  • Response key: products | service_apis | cfn_resources.

Not for region counts/docs/vague queries -- use search_documentation / list_regions.

Filter values must EXACTLY match AWS's catalog names; guessed, partial, or pluralized names are rejected ("values in filter parameter do not exist"). If unsure of the exact name, first call once for a single region with resource_type set and NO filters to list all valid names, then re-call filtering on the exact match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoUnused; use `regions`.
filtersNoUse exact AWS product or sub-feature name. - product: 'Amazon Bedrock' (service), or sub-features like 'Comprehend Auto Scaling', 'Latency-Based Routing', 'PrivateLink Support'. When the user names a specific sub-feature, filter on the sub-feature -- do NOT generalize to the parent service ('Amazon Comprehend'); that returns availability for the wrong scope. - api: 'SdkServiceId+Operation' (e.g. 'CloudFormation+CreateStack', 'IAM+GetSSHPublicKey') or 'SdkServiceId' (e.g. 'EC2'). Use a literal '+' between service and operation -- not space, colon, or hyphen. - cfn: 'AWS::EC2::Instance', 'AWS::Lambda::Function'. Include every region the user named; don't add filters they didn't request. Values must EXACTLY match AWS's catalog (e.g. 'AWS Lambda', not 'Lambda' or 'AWS Lambda Service'). If unsure of the exact name, first call once for one region with NO filters to list valid names, then filter on the exact match.
regionsNoAWS region codes (max 10). Multi-region requires `filters`; single-region supports `next_token`.
next_tokenNoPagination token. Single-region, no filters only.
resource_typeYesRequired: 'product' | 'api' | 'cfn'.

TDQS

A4.9/5.0
Behavior5/5

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

Adds rich behavioral context beyond annotations: exact-match filter requirements with error example, pagination via `next_token` (single-region/no filters), status values, and response keys. No contradiction with readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Bulleted, front-loaded structure with no fluff. Each sentence adds operational value—constraints, status, response keys, exclusions, and filter exact-match advice—all in a compact format.

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

Completeness5/5

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

For a tool with no output schema, the description covers critical aspects: valid statuses, response key names, pagination constraints, filter matching pitfalls, and a recovery strategy. Sufficiently complete for the tool's complexity.

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?

Schema already provides 100% parameter coverage, so baseline is 3. Description adds a concrete workflow for discovering exact filter names and warns against pluralized/partial values, which is beyond the schema. Slight extra value justifies 4.

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 it provides 'AWS resource availability per region' with specific statuses (isAvailableIn, isNotAvailableIn, etc.) and response keys. Explicitly distinguishes from siblings: 'Not for region counts/docs/vague queries -- use `search_documentation` / `list_regions`.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly states when not to use ('region counts/docs/vague queries') and names alternatives (`search_documentation`, `list_regions`). Also gives operational prerequisites: max 10 regions, multi-region requires `filters`, single-region supports `next_token`.

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

All AWS Knowledge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct aspect of AWS knowledge: regional availability, region listing, documentation search, full page retrieval, and skill retrieval. Descriptions clearly differentiate when to use each, especially distinguishing search from read_documentation.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case, prefixed by 'aws___.' Names like get_regional_availability, list_regions, read_documentation, retrieve_skill, and search_documentation are descriptive and predictable.

Tool Count5/5

Five tools is well-scoped for a knowledge server. Each tool provides a core function (search, full doc retrieval, region listing, availability check, skills) without redundancy or excessive specialization.

Completeness4/5

The tool set covers primary AWS knowledge needs: searching documentation, reading full pages, listing regions, checking regional availability, and retrieving skills. Minor gap: no direct tool for enumerating all services, but search_documentation can handle that.

Resources