Skip to main content
Glama
mnbro

outline-wiki-mcp

by mnbro

outline_capability_report

Read-onlyIdempotent

Return v0.2 control-plane capability metadata for Outline Wiki to validate connection and enable agentic diagnostics.

Instructions

Return v0.2 control-plane capability metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler that exposes outline_capability_report. It is decorated with @mcp.tool and calls the helper function capability_report().
    @mcp.tool(annotations=READ_ONLY)
    def outline_capability_report() -> dict[str, Any]:
        """Return v0.2 control-plane capability metadata."""
    
        return capability_report()
  • Helper function that resolves the config and calls build_capability_report() from the capability_report module, wrapping the result in a success response.
    def capability_report(config: Config | None = None) -> dict[str, Any]:
        """Return machine-readable component and tool metadata."""
    
        runtime_config = config or get_config()
        return success_response(build_capability_report(runtime_config))
  • Core builder function that constructs the full capability report dictionary, including component metadata, tool contracts, risk classes, and warnings.
    def build_capability_report(config: Config) -> dict[str, Any]:
        """Build the control-plane capability report."""
    
        available_tools = [tool["toolName"] for tool in TOOL_CONTRACTS]
        hidden_full_mode_tools: list[str] = []
        return {
            "componentId": "outline-wiki-mcp",
            "componentName": "Outline Wiki MCP",
            "componentType": "individual_mcp",
            "version": __version__,
            "schemaVersion": "0.2",
            "environment": config.environment,
            "mode": config.mcp_mode,
            "readOnly": config.read_only,
            "controlPlaneProfile": config.control_plane_profile,
            "businessDomain": "knowledge",
            "systemOwner": "CEO",
            "technicalOwner": "CEO",
            "safeDefaultMode": "agentic",
            "readOnlyDefault": True,
            "killSwitchStatus": "planned",
            "productionUseAllowed": False,
            "supportedTransports": ["stdio"],
            "availableTools": available_tools,
            "hiddenFullModeTools": hidden_full_mode_tools,
            "toolContracts": TOOL_CONTRACTS,
            "riskClasses": ["READ_ONLY"],
            "reversibilityClasses": ["R0"],
            "dataClassifications": ["internal"],
            "knownNoGoGates": [
                "read_only",
                "confirmation_required",
                "missing_capability_metadata",
                "secrets_exposure",
            ],
            "openFailureModes": [
                "OW-FM-001",
                "OW-FM-002",
                "OW-FM-003",
                "OW-FM-004",
                "OW-FM-005",
                "OW-FM-009",
                "OW-FM-010",
            ],
            "thresholdRegistryStatus": "baseline_planned",
            "productionConfidenceStatus": "not_production_ready",
            "warnings": [
                "TASK-001 bootstrap only.",
                "No production readiness, W3/W4/W5 maturity, or C5 conformance claimed.",
            ],
        }
  • The tool contract / schema definition for outline_capability_report in the TOOL_CONTRACTS list, specifying its metadata, risk class, allowed lanes, and governance attributes.
    {
        "toolName": "outline_capability_report",
        "description": "Report v0.2 control-plane metadata.",
        "category": "Diagnostics",
        "riskClass": "READ_ONLY",
        "reversibilityClass": "R0",
        "dataClassification": "internal",
        "externalEffect": False,
        "modeExposure": "agentic",
        "allowedLanes": [
            "direct_mcp_lane",
            "production_confidence_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": True,
        "auditEvents": ["capability_report_read"],
        "policyGates": [],
        "noGoGates": ["missing_capability_metadata"],
        "rollbackAvailable": None,
        "compensationRequired": False,
        "killSwitchAffected": False,
        "owner": "CEO",
        "status": "implemented",
        "version": __version__,
    },
  • The tool is listed as an implemented tool in the diagnostics function output, representing its registration in the server.
    "implementedTools": [
        "outline_validate_connection",
        "outline_capability_report",
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering safety and behavior. The description adds only the version hint ('v0.2'), which provides minor additional context beyond the annotations.

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, self-contained sentence that is front-loaded and contains no unnecessary words. It is highly concise.

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

Completeness4/5

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

Given zero parameters and the presence of an output schema, the description is adequate but could be slightly more informative about what 'capability metadata' entails. It is nearly complete for a simple metadata retrieval tool.

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 zero parameters, so the description does not need to add parameter meaning. Baseline for 0 parameters is 4, and no further elaboration is required.

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 uses a specific verb ('Return') and resource ('control-plane capability metadata') with versioning ('v0.2'), clearly distinguishing it from siblings like outline_diagnostics and outline_validate_connection.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any context or exclusion criteria.

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