Skip to main content
Glama
mnbro

outline-wiki-mcp

by mnbro

outline_validate_connection

Read-onlyIdempotent

Validate Outline API token and connectivity to confirm secure access and readiness for operations.

Instructions

Validate Outline token and API connectivity safely.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler registered as @mcp.tool, delegates to validate_connection()
    @mcp.tool(annotations=READ_ONLY)
    async def outline_validate_connection() -> dict[str, Any]:
        """Validate Outline token and API connectivity safely."""
    
        return await validate_connection()
  • Core validation logic: checks config, calls OutlineClient.validate_connection(), returns success/error response
    async def validate_connection(config: Config | None = None) -> dict[str, Any]:
        """Validate Outline configuration and API connectivity safely."""
    
        runtime_config = config or get_config()
        if not runtime_config.normalized_base_url:
            return error_response(
                "configuration_missing",
                "OUTLINE_BASE_URL is not configured.",
                action="Set OUTLINE_BASE_URL to the Outline workspace URL.",
                blockers=["Missing OUTLINE_BASE_URL"],
                no_go_gate="configuration_missing",
            )
        if not runtime_config.api_token:
            return error_response(
                "configuration_missing",
                "OUTLINE_API_TOKEN is not configured.",
                action="Set OUTLINE_API_TOKEN to a valid Outline API token.",
                blockers=["Missing OUTLINE_API_TOKEN"],
                no_go_gate="configuration_missing",
            )
        try:
            async with OutlineClient(runtime_config) as client:
                payload = await client.validate_connection()
        except OutlineAPIError as exc:
            return error_response(
                exc.error_type,
                str(exc),
                action="Verify OUTLINE_BASE_URL, OUTLINE_API_TOKEN, and Outline API permissions.",
                warnings=[f"statusCode={exc.status_code}"] if exc.status_code else [],
                no_go_gate="upstream_connection_failed",
            )
        except ValueError as exc:
            return error_response(
                "configuration_invalid",
                str(exc),
                action="Review OUTLINE_BASE_URL and OUTLINE_API_TOKEN.",
                no_go_gate="configuration_invalid",
            )
        return success_response(
            {
                "connected": True,
                "baseUrl": runtime_config.normalized_base_url,
                "outlineResponse": redact_secrets(payload),
            },
            next_action="Use read-only diagnostics or capability report before enabling write-capable tools.",
        )
  • Client-level method that performs the actual RPC call to Outline's auth.info endpoint
    async def validate_connection(self) -> dict[str, Any]:
        """Run a safe read-only auth/workspace info probe."""
    
        return await self.post_rpc("auth.info")
  • Capability contract/registry entry for outline_validate_connection tool
    TOOL_CONTRACTS: list[dict[str, Any]] = [
        {
            "toolName": "outline_validate_connection",
            "description": "Validate token and API connectivity safely.",
            "category": "Diagnostics",
            "riskClass": "READ_ONLY",
            "reversibilityClass": "R0",
            "dataClassification": "internal",
            "externalEffect": False,
            "modeExposure": "agentic",
            "allowedLanes": ["direct_mcp_lane", "investigation_lane"],
            "allowedOperatingModes": [
                "startup",
                "growth",
                "mature",
                "crisis_alert_state_read_only",
            ],
            "readOnlySafe": True,
            "dryRunDefault": None,
            "requiresConfirmation": False,
            "requiredApprovalLevel": "none",
            "requiresApprovalPack": False,
            "requiresDecisionRecord": False,
            "productionConfidenceRequired": False,
            "auditEvents": ["optional_read"],
            "policyGates": [],
            "noGoGates": [],
            "rollbackAvailable": None,
            "compensationRequired": False,
            "killSwitchAffected": False,
            "owner": "CEO",
            "status": "implemented",
            "version": __version__,
        },
  • Tool name listed in diagnostics implementedTools list
    "implementedTools": [
        "outline_validate_connection",
        "outline_capability_report",
        "outline_diagnostics",
    ],
    "notImplementedInTask001": [
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, which cover safety and idempotency. The description adds the word 'safely', but no additional behavioral traits beyond what annotations provide.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the tool's 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?

For a simple validation tool with no parameters and an existing output schema, the description sufficiently covers what the tool does. No additional context is needed.

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 tool has no parameters, so the description does not need to explain parameter semantics. Baseline score of 4 is appropriate.

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 validates an Outline token and API connectivity, using a specific verb and resource. It distinguishes itself from siblings like outline_capability_report and outline_diagnostics.

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 implies this is a safe check to perform before other operations, but it does not explicitly state when to use it versus alternatives, nor does it mention exclusions. The straightforward nature of the tool makes this a minor gap.

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/mnbro/outline-wiki-mcp'

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