Skip to main content
Glama
CSOAI-ORG

API Docs Generator AI MCP

add_auth_to_spec

Add an authentication scheme (bearer, api_key, basic, or oauth2) to an OpenAPI specification to define security for your API endpoints.

Instructions

Add authentication scheme to an OpenAPI spec. auth_type: bearer, api_key, basic, oauth2.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results.

Args: spec_json (str): The spec json to analyze or process. auth_type (str): The auth type to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spec_jsonYes
auth_typeNobearer
api_keyNo

Implementation Reference

  • server.py:319-319 (registration)
    The @mcp.tool() decorator immediately above line 256 registers 'add_auth_to_spec' as an MCP tool named 'add_auth_to_spec'.
    return {"spec": spec}
  • Main handler for add_auth_to_spec tool. Parses spec_json as JSON, validates auth_type against supported schemes (bearer, api_key, basic, oauth2), injects securitySchemes and security into the OpenAPI spec, and returns the augmented spec.
    def add_auth_to_spec(spec_json: str, auth_type: str = "bearer", api_key: str = "") -> dict:
        """Add authentication scheme to an OpenAPI spec. auth_type: bearer, api_key, basic, oauth2.
    
        Behavior:
            This tool is read-only and stateless — it produces analysis output
            without modifying any external systems, databases, or files.
            Safe to call repeatedly with identical inputs (idempotent).
            Free tier: 10/day rate limit. Pro tier: unlimited.
            No authentication required for basic usage.
    
        When to use:
            Use this tool when you need structured analysis or classification
            of inputs against established frameworks or standards.
    
        When NOT to use:
            Not suitable for real-time production decision-making without
            human review of results.
    
        Args:
            spec_json (str): The spec json to analyze or process.
            auth_type (str): The auth type to analyze or process.
            api_key (str): The api key to analyze or process.
    
        Behavioral Transparency:
            - Side Effects: This tool is read-only and produces no side effects. It does not modify
              any external state, databases, or files. All output is computed in-memory and returned
              directly to the caller.
            - Authentication: No authentication required for basic usage. Pro/Enterprise tiers
              require a valid MEOK API key passed via the MEOK_API_KEY environment variable.
            - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are
              included in responses (X-RateLimit-Remaining, X-RateLimit-Reset).
            - Error Handling: Returns structured error objects with 'error' key on failure.
              Never raises unhandled exceptions. Invalid inputs return descriptive validation errors.
            - Idempotency: Fully idempotent — calling with the same inputs always produces the
              same output. Safe to retry on timeout or transient failure.
            - Data Privacy: No input data is stored, logged, or transmitted to external services.
              All processing happens locally within the MCP server process.
        """
        allowed, msg, tier = check_access(api_key)
        if not allowed:
            return {"error": msg, "upgrade_url": "https://meok.ai/pricing"}
    
        if not _check_rate():
            return {"error": "Rate limit exceeded (50/day)"}
        try:
            spec = json.loads(spec_json)
        except json.JSONDecodeError:
            return {"error": "Invalid JSON for spec"}
        schemes = {
            "bearer": {"type": "http", "scheme": "bearer", "bearerFormat": "JWT"},
            "api_key": {"type": "apiKey", "in": "header", "name": "X-API-Key"},
            "basic": {"type": "http", "scheme": "basic"},
            "oauth2": {
                "type": "oauth2",
                "flows": {"authorizationCode": {"authorizationUrl": "https://example.com/oauth/authorize", "tokenUrl": "https://example.com/oauth/token", "scopes": {"read": "Read access", "write": "Write access"}}},
            },
        }
        if auth_type not in schemes:
            return {"error": f"Unknown auth type: {auth_type}. Use: bearer, api_key, basic, oauth2"}
        if "components" not in spec:
            spec["components"] = {}
        spec["components"]["securitySchemes"] = {auth_type: schemes[auth_type]}
        spec["security"] = [{auth_type: []}]
        return {"spec": spec}
Behavior1/5

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

The description claims the tool is 'read-only and stateless' yet its name and purpose imply modification. This internal contradiction severely undermines transparency. No annotations exist to clarify.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and repetitive, with a 'Behavior' section that largely duplicates the 'Behavioral Transparency' section. Structure is poor and could be more concise.

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

Completeness1/5

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

The description fails to explain the output format, how the auth is incorporated into the spec, or criteria for success/failure. Essential context is missing, and the contradictory read-only claim adds confusion.

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?

With 0% schema description coverage, the description only provides generic phrases like 'to analyze or process' for each parameter, adding no meaningful detail beyond what the schema already shows.

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 clearly states the tool adds an authentication scheme to an OpenAPI spec, listing specific auth types (bearer, api_key, basic, oauth2). This distinguishes it from sibling tools like generate_endpoint or validate_spec.

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 'When to use' section is mismatched, referring to 'structured analysis or classification' rather than adding auth. No explicit alternatives are given, and the guidance is vague.

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/CSOAI-ORG/api-docs-generator-ai-mcp'

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