Skip to main content
Glama

integration_catalog

Read-onlyIdempotent

Search the official AWS MCP catalog snapshot to discover integration entries and compare available AWS tools; returned entries are discovery references, not hosted or executed tools.

Instructions

Search the snapshot of the complete official AWS MCP catalog. Discovery entries are not hosted/executed tools.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault
totalNo
sourceNo
serversNo
boundaryNo
retrievedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / required
      Removed value: -[
      -  "query",
      -  "limit"
      -]
  2. First observedv0.4.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add context. It does: calling the data a 'snapshot' warns that results may be stale, and the note that entries are discovery-only and not hosted/executed tools prevents a costly misreading. It omits ranking, matching, and default-result behavior, which keeps it short of a 5.

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?

Two short sentences, the core action front-loaded, and the caveat placed second where it qualifies rather than obscures. No filler or repetition of the name.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the tool is simple with two optional parameters. Still, the description never explains how search matching works or what the catalog snapshot covers, which matters for a search tool with an empty query default.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden for 'query' and 'limit', and it says nothing about either. An agent gets no guidance on whether 'query' is keyword, substring, or full-text matching, nor on how 'limit' (max 70, default 20) affects results.

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 description gives a specific verb and resource: 'Search the snapshot of the complete official AWS MCP catalog.' The second sentence ('Discovery entries are not hosted/executed tools') usefully separates it from tools that actually run or review MCP servers, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is for discovering catalog entries rather than reviewing or configuring an MCP server. There is no explicit 'use this when...' clause, no mention of when to prefer aws_knowledge_search or mcp_server_review, and no prerequisite or exclusion stated.

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