Skip to main content
Glama
Joseph19820124

AWS Documentation MCP Server

by Joseph19820124
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

recommend

Get content recommendations for an AWS documentation page, including highly rated, new, similar, and journey categories to discover related content.

Instructions

Get content recommendations for an AWS documentation page.

## Usage

This tool provides recommendations for related AWS documentation pages based on a given URL.
Use it to discover additional relevant content that might not appear in search results.

## Recommendation Types

The recommendations include four categories:

1. **Highly Rated**: Popular pages within the same AWS service
2. **New**: Recently added pages within the same AWS service - useful for finding newly released features
3. **Similar**: Pages covering similar topics to the current page
4. **Journey**: Pages commonly viewed next by other users

## When to Use

- After reading a documentation page to find related content
- When exploring a new AWS service to discover important pages
- To find alternative explanations of complex concepts
- To discover the most popular pages for a service
- To find newly released information by using a service's welcome page URL and checking the **New** recommendations

## Finding New Features

To find newly released information about a service:
1. Find any page belong to that service, typically you can try the welcome page
2. Call this tool with that URL
3. Look specifically at the **New** recommendation type in the results

## Result Interpretation

Each recommendation includes:
- url: The documentation page URL
- title: The page title
- context: A brief description (if available)

Args:
    ctx: MCP context for logging and error handling
    url: URL of the AWS documentation page to get recommendations for

Returns:
    List of recommended pages with URLs, titles, and context

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the AWS documentation page to get recommendations for

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It describes four recommendation types (Highly Rated, New, Similar, Journey), how to interpret results (url, title, context), and specific usage context (e.g., using welcome pages). It does not disclose side effects or rate limits, but the behavior is well-explained.

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?

The description is well-structured with sections (Usage, Recommendation Types, When to Use, Finding New Features, Result Interpretation) and bullet points. It is somewhat long but every sentence adds value and is front-loaded with the core purpose.

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?

Given no output schema, the description explains the return structure (url, title, context) and the four recommendation categories. The tool has only one parameter and is simple, so the description is sufficiently complete for an agent to understand and invoke it correctly.

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% (only param 'url' with description). The description reinforces the param's meaning by specifying it as an 'AWS documentation page URL' and provides usage examples (e.g., welcome page). It adds value beyond the schema.

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?

The description explicitly states 'Get content recommendations for an AWS documentation page' and distinguishes from sibling tools (read_documentation, search_documentation) by focusing on recommendations based on a URL.

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 description provides a 'When to Use' section with concrete scenarios (after reading a page, exploring a new service, finding new features) and includes a step-by-step guide for finding new features. It does not explicitly mention when not to use or compare to alternatives, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Joseph19820124/aws-doc-sse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server