developer-docs Static interface comparison

AWS Documentation MCP

1.2.4 1.2.5

PASSAutomated static analysis

No policy-significant interface change detected.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools5 → 5
Added0
Removed0
Schema changes0
Input schema changes0
Output schema changes0
Unclassified schema changes0
Description changes4
New write authority0
New destructive authority0
New unknown authority0
AnalysisPASS

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

4 tools with recorded changes

  1. read_documentationModifiedDescriptionINFO

    What changed

    • read_documentation: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousFetch and convert an AWS documentation page to markdown format. ## Usage This tool retrieves the content of an AWS documentation page and converts it to markdown format. For long documents, you can make multiple calls with different start_index values to retrieve the entire content in chunks. ## URL Requirements - Must be from the docs.aws.amazon.com domain - Must end with .html ## Example URLs - https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html - https://docs.aws.amazon.com/lambda/latest/dg/lambda-invocation.html ## Output Format The output is formatted as markdown text with: - Preserved headings and structure - Code blocks for examples - Lists and tables converted to markdown format ## Large Tables Tables with more than 20 rows are automatically truncated to show only the header and 5 sample rows, along with a hint to use the `search_table` tool. Use `search_table` to filter and retrieve specific rows from large tables (e.g., service quotas, IAM actions). ## Handling Long Documents If the response indicates the document was truncated, you have several options: 1. **Continue Reading**: Make another call with start_index set to the end of the previous response 2. **Stop Early**: For very long documents (>30,000 characters), if you've already found the specific information needed, you can stop reading Args: ctx: MCP context for logging and error handling url: URL of the AWS documentation page to read max_length: Maximum number of characters to return start_index: On return output starting at this character index Returns: Markdown content of the AWS documentation
    CurrentFetch and convert an AWS documentation page to markdown format. ## Usage This tool retrieves the content of an AWS documentation page and converts it to markdown format. For long documents, you can make multiple calls with different start_index values to retrieve the entire content in chunks. ## URL Requirements - Must be from the docs.aws.amazon.com domain - Must end with .html or .md ## Example URLs - https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html - https://docs.aws.amazon.com/lambda/latest/dg/lambda-invocation.html ## Output Format The output is formatted as markdown text with: - Preserved headings and structure - Code blocks for examples - Lists and tables converted to markdown format - Links to other pages kept as published, often relative (e.g. `invocation-sync.md`); resolve a relative link against the page URL before reading it ## Large Tables Tables with more than 20 rows are automatically truncated to show only the header and 5 sample rows, along with a hint to use the `search_table` tool. Use `search_table` to filter and retrieve specific rows from large tables (e.g., service quotas, IAM actions). ## Handling Long Documents If the response indicates the document was truncated, you have several options: 1. **Continue Reading**: Make another call with start_index set to the end of the previous response 2. **Stop Early**: For very long documents (>30,000 characters), if you've already found the specific information needed, you can stop reading Args: ctx: MCP context for logging and error handling url: URL of the AWS documentation page to read max_length: Maximum number of characters to return start_index: On return output starting at this character index Returns: Markdown content of the AWS documentation

    Input schema

    Input schema unchanged.

    4 unchanged entries
    • (schema root)
    • max_length
    • start_index
    • url

    Output schema

    Output schema unchanged.

    2 unchanged entries
    • (schema root)
    • result
    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  2. read_sectionsModifiedDescriptionINFO

    What changed

    • read_sections: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousExtract specific sections from AWS documentation pages by title. Retrieves a page, converts to markdown, and returns only matching sections. Section matching is case-insensitive and handles whitespace differences. ## URL Requirements - Must end with .html ## Large Tables Tables with more than 20 rows are automatically truncated to show only the header and 5 sample rows, along with a hint to use the `search_table` tool. Use `search_table` to filter and retrieve specific rows from large tables (e.g., service quotas, IAM actions). ## Read Sections Tips - Use exact section titles from search results 'sections' field when available - Section matching is case-insensitive and handles whitespace differences - Include multiple related sections in one call for comprehensive coverage ## Example Usage ``` # If query is about S3 bucket naming rules: # Available sections: ['General purpose buckets naming rules', 'Example general purpose bucket names', 'Best practices', 'Creating a bucket that uses a GUID in the bucket name'] # Read these specific sections: read_sections( url='https://docs.aws.amazon.com/s3/latest/userguide/bucketnamingrules.html', section_titles=['General purpose buckets naming rules', 'Best practices'], ) # If query is about Python Lambda function examples: # Available sections: ['Example Python Lambda function code', 'Handler naming conventions', 'Using the Lambda event object', 'Accessing and using the Lambda context object'. 'Valid handler signatures for Python handlers', 'Returning a value', 'Using the AWS SDK for Python (Boto3) in your handler', 'Accessing environment variables, 'Code best practices for Python Lambda functions'] # Read these specific sections: read_sections( url='https://docs.aws.amazon.com/lambda/latest/dg/python-handler.html', section_titles=[ 'Example Python Lambda function code', 'Code best practices for Python Lambda functions', ], ) ``` Args: ctx: MCP context for logging and error handling url: URL of the AWS documentation page to read section_titles: List of section titles to extract Returns: Filtered markdown content containing only the requested sections
    CurrentExtract specific sections from AWS documentation pages by title. Retrieves a page, converts to markdown, and returns only matching sections. Section matching is case-insensitive and handles whitespace differences. A title can be a heading at any level. Each section runs to the next heading at the same or a higher level, so it includes its subsections. A title that names only the page returns the whole page, paginated like read_documentation; if the page title is also a section heading, those sections are returned instead. ## URL Requirements - Must end with .html or .md ## Large Tables Tables with more than 20 rows are automatically truncated to show only the header and 5 sample rows, along with a hint to use the `search_table` tool. Use `search_table` to filter and retrieve specific rows from large tables (e.g., service quotas, IAM actions). ## Read Sections Tips - Use exact section titles from search results 'sections' field when available - Section matching is case-insensitive and handles whitespace differences - Include multiple related sections in one call for comprehensive coverage - Links to other pages are kept as published, often relative (e.g. `invocation-sync.md`); resolve a relative link against the page URL before reading it ## Example Usage ``` # If query is about S3 bucket naming rules: # Available sections: ['General purpose buckets naming rules', 'Example general purpose bucket names', 'Best practices', 'Creating a bucket that uses a GUID in the bucket name'] # Read these specific sections: read_sections( url='https://docs.aws.amazon.com/s3/latest/userguide/bucketnamingrules.html', section_titles=['General purpose buckets naming rules', 'Best practices'], ) # If query is about Python Lambda function examples: # Available sections: ['Example Python Lambda function code', 'Handler naming conventions', 'Using the Lambda event object', 'Accessing and using the Lambda context object'. 'Valid handler signatures for Python handlers', 'Returning a value', 'Using the AWS SDK for Python (Boto3) in your handler', 'Accessing environment variables, 'Code best practices for Python Lambda functions'] # Read these specific sections: read_sections( url='https://docs.aws.amazon.com/lambda/latest/dg/python-handler.html', section_titles=[ 'Example Python Lambda function code', 'Code best practices for Python Lambda functions', ], ) ``` Args: ctx: MCP context for logging and error handling url: URL of the AWS documentation page to read section_titles: List of section titles to extract Returns: Filtered markdown content containing only the requested sections

    Input schema

    Input schema unchanged.

    4 unchanged entries
    • (schema root)
    • section_titles
    • section_titles › [items]
    • url

    Output schema

    Output schema unchanged.

    2 unchanged entries
    • (schema root)
    • result
    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  3. recommendModifiedDescriptionINFO

    What changed

    • recommend: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousGet 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 three categories: 1. **New**: Recently added pages within the same AWS service - useful for finding newly released features 2. **Similar**: Pages covering similar topics to the current page 3. **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 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
    CurrentGet 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 three categories: 1. **New**: Recently added pages within the same AWS service - useful for finding newly released features 2. **Similar**: Pages covering similar topics to the current page 3. **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 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 ## URL Requirements - Must be from the docs.aws.amazon.com domain - A .md page URL, such as a link followed from read_documentation output, is looked up as its .html page ## 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

    Input schema unchanged.

    2 unchanged entries
    • (schema root)
    • url

    Output schema

    Output schema unchanged.

    3 unchanged entries
    • (schema root)
    • result
    • result › [items]
    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  4. search_tableModifiedDescriptionINFO

    What changed

    • search_table: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    unknown → unknown
    Description
    PreviousSearch for specific rows in a large documentation table. Use this tool when you need specific rows from a large documentation table (e.g., service quotas, pricing tables, supported models lists). Returns matching rows as JSON instead of dumping the entire table. This is more efficient than read_sections for pages with hundreds of table rows. If read_sections or read_documentation indicates a table was truncated, use this tool to find the specific rows you need. ## Section Title - If you know the exact section title, provide it for precision - If unsure, omit section_title — the tool will search all tables on the page - Use section titles from search_documentation results (TOC) or read_documentation output - If the section title is wrong, the hint field will list available sections ## URL Requirements - Must be from the docs.aws.amazon.com domain - Must end with .html ## Example Usage ``` # With section title (searches all tables in that section): search_table( url='https://docs.aws.amazon.com/general/latest/gr/bedrock.html', section_title='Amazon Bedrock service quotas', query='Titan Text Embeddings V2', ) # Without section title (searches all tables on the page): search_table( url='https://docs.aws.amazon.com/general/latest/gr/bedrock.html', query='Claude 3 Sonnet requests', ) ``` ## Response Format Returns a SearchTableResponse with: - tables_searched: Number of tables searched - tables_with_matches: Number of tables containing matching rows - hint: Guidance message when no matches found, section not found, or no tables on page - results: Array of table result objects, each with: - table_heading: The sub-heading above the table (if any) - columns: Column headers for that table - parent_columns: (optional) For rowspan/nested tables, which columns are group headers - child_columns: (optional) For rowspan/nested tables, which columns are nested under groups - total_rows: Total rows (or groups, for nested tables) in that table - matched_rows: Number of rows/groups matching the query per table - showing: Number of rows/groups returned per table (capped by max_rows per table) - rows: Array of matching row objects. For flat tables: {column → value}. For nested tables: {parent_col → value, ..., "rows": [{child_col → value}, ...]} Args: ctx: MCP context for logging and error handling url: AWS documentation page URL (must end with .html) section_title: The section heading containing the table (optional — omit to search all tables on the page) query: Search term to filter rows (all words must match, case-insensitive) max_rows: Maximum matching rows to return per table (default 20) Returns: SearchTableResponse with matching rows grouped by table
    CurrentSearch for specific rows in a large documentation table. Use this tool when you need specific rows from a large documentation table (e.g., service quotas, pricing tables, supported models lists). Returns matching rows as JSON instead of dumping the entire table. This is more efficient than read_sections for pages with hundreds of table rows. If read_sections or read_documentation indicates a table was truncated, use this tool to find the specific rows you need. ## Section Title - If you know the exact section title, provide it for precision - If unsure, omit section_title — the tool will search all tables on the page - Use section titles from search_documentation results (TOC) or read_documentation output - If the section title is wrong, the hint field will list available sections ## URL Requirements - Must be from the docs.aws.amazon.com domain - Must end with .html or .md ## Example Usage ``` # With section title (searches all tables in that section): search_table( url='https://docs.aws.amazon.com/general/latest/gr/bedrock.html', section_title='Amazon Bedrock service quotas', query='Titan Text Embeddings V2', ) # Without section title (searches all tables on the page): search_table( url='https://docs.aws.amazon.com/general/latest/gr/bedrock.html', query='Claude 3 Sonnet requests', ) ``` ## Response Format Returns a SearchTableResponse with: - tables_searched: Number of tables searched - tables_with_matches: Number of tables containing matching rows - hint: Guidance message when no matches found, section not found, or no tables on page - results: Array of table result objects, each with: - table_heading: The sub-heading above the table (if any) - columns: Column headers for that table - parent_columns: (optional) For rowspan/nested tables, which columns are group headers - child_columns: (optional) For rowspan/nested tables, which columns are nested under groups - total_rows: Total rows (or groups, for nested tables) in that table - matched_rows: Number of rows/groups matching the query per table - showing: Number of rows/groups returned per table (capped by max_rows per table) - rows: Array of matching row objects. For flat tables: {column → value}. For nested tables: {parent_col → value, ..., "rows": [{child_col → value}, ...]} Args: ctx: MCP context for logging and error handling url: AWS documentation page URL (must end with .html or .md) section_title: The section heading containing the table (optional — omit to search all tables on the page) query: Search term to filter rows (all words must match, case-insensitive) max_rows: Maximum matching rows to return per table (default 20) Returns: SearchTableResponse with matching rows grouped by table

    Input schema

    Input schema unchanged.

    5 unchanged entries
    • (schema root)
    • max_rows
    • query
    • section_title
    • url

    Output schema

    Output schema unchanged.

    9 unchanged entries
    • (schema root)
    • hint
    • query
    • results
    • results › [items]
    • section_title
    • tables_searched
    • tables_with_matches
    • url
    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
1 tool with no recorded change
  • search_documentation

Evidence and provenance

Static findings
PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Automated static analysis. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
aws-documentation/1.2.4~1.2.5The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 10, 2026, 1:18 AM UTC.
Distribution
pypi
Previous release
awslabs.aws-documentation-mcp-server@1.2.45 tools · published by the registry Oct 30, 2026, 8:56 PM UTC · upstream 1.2.4Artifact integritysha256-+RAVc4B99LhSIBwQjqOLwCxnJNHlHg3jVKOOB3nO4LY=Artifactawslabs_aws_documentation_mcp_server-1.2.4-py3-none-any.whlInterface fingerprintsha256:24f03ee1a2d19a7b6c84a81f3d7f214d5cd9fabb45656b556a093f3422513eb9Exact interface snapshot (JSON)
Current release
awslabs.aws-documentation-mcp-server@1.2.55 tools · published by the registry Nov 9, 2026, 9:57 PM UTC · upstream 1.2.5Artifact integritysha256-rc68p9k6t3r+vOT8a0Cc7+EnnVqnwseqq9vqsQEna5Q=Artifactawslabs_aws_documentation_mcp_server-1.2.5-py3-none-any.whlInterface fingerprintsha256:0cd3c88913c21e24c7785c140a4df8bfde02ead137cbf253ebb9d09f764fc6c4Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 10, 2026

Informational

4 findings
  • read_documentationINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
  • read_sectionsINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
  • recommendINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
  • search_tableINFOChanged

    Description changed

    Authority
    UNKNOWNUNKNOWN
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to AWS Documentation MCP release history