Skip to main content
Glama

NS Pros MCP Gateway

aws-mcp__aws___get_regional_availability

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 unsur

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": {
      "resource_type": "<resource_type>"
    },
    "name": "aws-mcp__aws___get_regional_availability"
  }
}

Input 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'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 10-region cap, the filters-required condition for multi-region calls, the pagination restriction, and the server-side rejection behavior for inexact filter values including the error string. It does not state that the operation is read-only or mention latency/rate characteristics, leaving a modest gap.

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?

Bullet structure is front-loaded, with constraints and status vocabulary before caveats, and almost every line carries actionable content. The final sentence is cut off mid-thought ('If unsure'), leaving a dangling fragment that should have been completed or removed.

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 appropriately names the response keys (products | service_apis | cfn_resources) and enumerates status values. Combined with the parameter constraints this is enough to call the tool correctly, though the truncated closing sentence and the lack of any statement about whether results cover all regions or only the requested ones leave small gaps.

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 coverage is 100%, so the baseline is 3; the description goes beyond it by warning that the `region` parameter is unused, by tying `regions` count to the `filters` requirement, and by restricting `next_token` usage. The filter-name exact-match semantics and the 'filter on the sub-feature, not the parent service' rule add real interpretive value on top of the schema text.

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?

The opening line 'AWS resource availability per region' names the resource and scope precisely, and the status/response-key bullets make the returned data shape concrete. It is not a verb-first statement (no 'check'/'get') and never states the three resource_type modes in the summary line, so it falls just short of a 5.

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?

Explicit exclusions are given with named alternatives: 'Not for region counts/docs/vague queries -- use search_documentation / list_regions'. It also states the operational preconditions (max 10 regions, multi-region requires filters, next_token only for single-region without filters) and even prescribes a discovery workflow when exact catalog names are unknown.

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.