Skip to main content
Glama

get-api-catalog

Retrieve the API catalog containing metadata for all OpenAPI specifications, operations, and schemas to enable AI-powered development tools to understand and work with your APIs.

Instructions

Get the API catalog, the catalog contains metadata about all openapi specifications, their operations and schemas

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the MCP tool 'get-api-catalog' including its description and handler function. The handler fetches the API catalog from the specExplorer and serializes it to YAML text for response.
    server.tool(
      "get-api-catalog",
      "Get the API catalog, the catalog contains metadata about all openapi specifications, their operations and schemas",
      async () => {
        try {
          this.logger.debug('Getting API catalog');
          const catalog = await this.specExplorer.getApiCatalog();
          return {
            content: [
              { type: "text", text: stringify({ catalog }, { indent: 2 }) },
            ],
          };
        } catch (error) {
          this.logger.error('Failed to get API catalog', { error });
          throw error;
        }
      }
    );
  • Implementation of the getApiCatalog method in FileSystemSpecService (implements ISpecExplorer), which returns the pre-built catalog of discovered API specifications.
    async getApiCatalog(): Promise<SpecCatalogEntry[]> {
      return this.catalog;
    }
  • Type signature of getApiCatalog method in ISpecExplorer interface, returning Promise<SpecCatalogEntry[]>.
    /**
     * List all specifications in the catalog
     */
    getApiCatalog(): Promise<SpecCatalogEntry[]>;
  • Type definition for SpecCatalogEntry, the core data structure of the API catalog returned by getApiCatalog.
    export interface SpecCatalogEntry {
      /** URI identifying the specification */
      uri: SpecUri;
      /** Optional description of the specification */
      description?: string;
      /** List of operations in the specification */
      operations: SpecOperationEntry[];
      /** List of schemas in the specification */
      schemas: SpecSchemaEntry[];
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves metadata but doesn't cover critical aspects like whether it's read-only, requires authentication, has rate limits, returns paginated results, or handles errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core purpose ('Get the API catalog') and adds clarifying details about the catalog's contents. It avoids unnecessary words, though it could be slightly more structured by explicitly separating purpose from content explanation.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It explains what the tool does but omits behavioral details (e.g., read-only nature, response format, error handling) and doesn't reference sibling tools. For a tool in a context with multiple related tools and no structured safety hints, this leaves the agent under-informed.

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?

The input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of parameters. The description doesn't add parameter-specific information, but since there are no parameters, a baseline score of 4 is appropriate as it doesn't need to compensate for any gaps.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('API catalog'), and it explains what the catalog contains (metadata about OpenAPI specifications, operations, and schemas). However, it doesn't explicitly differentiate from sibling tools like 'refresh-api-catalog' (which might update the catalog) or 'search-api-operations' (which might filter operations), so it doesn't reach a score of 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'refresh-api-catalog' for updating the catalog or 'search-api-operations' for filtering operations, nor does it specify prerequisites or exclusions. This leaves the agent without clear usage context.

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/ReAPI-com/mcp-openapi'

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