Skip to main content
Glama
hackIDLE

FedRAMP Docs MCP Server

by hackIDLE

health_check

Check the FedRAMP Docs MCP Server's operational status to verify index readiness, display file counts, repository details, and update settings for compliance analysis.

Instructions

Verify the index is ready and report status. Returns: indexed file count, repository path, FedRAMP docs commit hash and date, last update check time, and auto-update settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the health_check tool logic: retrieves index state, counts indexed files (FRMR + Markdown), fetches repo commit info asynchronously, gets auto-update config, determines if healthy (no errors), and returns structured status.
    export async function healthCheck(): Promise<{
      ok: boolean;
      indexedFiles: number;
      repoPath: string;
      errors?: string[];
      repoInfo?: RepoInfo;
      autoUpdate?: AutoUpdateConfig;
    }> {
      const state = getIndexState();
      const indexedFiles =
        state.frmrDocuments.length + state.markdownDocs.size;
      const errors = getIndexErrors();
    
      // Get repo info (commit hash, date, last fetch time)
      const repoInfoResult = await getRepoInfo();
      const repoInfo: RepoInfo | undefined = repoInfoResult
        ? {
            commitHash: repoInfoResult.commitHash,
            commitDate: repoInfoResult.commitDate,
            lastFetchedAt: repoInfoResult.lastFetchedAt,
          }
        : undefined;
    
      // Get auto-update configuration
      const autoUpdateConfig = getAutoUpdateConfig();
      const autoUpdate: AutoUpdateConfig = {
        enabled: autoUpdateConfig.enabled,
        checkIntervalHours: autoUpdateConfig.checkIntervalHours,
      };
    
      return {
        ok: errors.length === 0,
        indexedFiles,
        repoPath: state.repoPath,
        errors: errors.length ? errors : undefined,
        repoInfo,
        autoUpdate,
      };
    }
  • ToolDefinition for 'health_check': defines name, description, empty input schema, and execute handler that delegates to the core healthCheck function.
    export const healthCheckTool: ToolDefinition<
      typeof schema,
      Awaited<ReturnType<typeof healthCheck>>
    > = {
      name: "health_check",
      description:
        "Verify the index is ready and report status. Returns: indexed file count, repository path, FedRAMP docs commit hash and date, last update check time, and auto-update settings.",
      schema,
      execute: async () => healthCheck(),
    };
  • Zod input schema for health_check tool: empty object (no parameters).
    const schema = z.object({});
  • TypeScript interface defining the output structure of the health_check tool result.
    export interface HealthCheckResult {
      ok: boolean;
      indexedFiles: number;
      repoPath: string;
      errors?: string[];
      repoInfo?: RepoInfo;
      autoUpdate?: AutoUpdateConfig;
    }
  • Registers the healthCheckTool (along with others) to the MCP server via registerToolDefs.
    export function registerTools(server: McpServer): void {
      registerToolDefs(server, [
        // Document discovery
        listFrmrDocumentsTool,
        getFrmrDocumentTool,
        listVersionsTool,
        // KSI tools
        listKsiTool,
        getKsiTool,
        filterByImpactTool,
        getThemeSummaryTool,
        getEvidenceExamplesTool,
        // Control mapping tools
        listControlsTool,
        getControlRequirementsTool,
        analyzeControlCoverageTool,
        // Search & lookup tools
        searchMarkdownTool,
        readMarkdownTool,
        searchDefinitionsTool,
        getRequirementByIdTool,
        // Analysis tools
        diffFrmrTool,
        grepControlsTool,
        significantChangeTool,
        // System tools
        healthCheckTool,
        updateRepositoryTool,
      ]);
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses what the tool returns (indexed file count, repository path, etc.), which is useful behavioral context. However, it doesn't mention error conditions, performance characteristics, or whether this is a read-only operation (though implied by 'verify' and 'report').

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 two sentences: one stating the purpose and one detailing the return values. It's appropriately sized and front-loaded with the core function. However, the second sentence is a bit dense with multiple return items listed, which slightly affects readability.

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?

Given the tool's complexity (simple status check with 0 params), no annotations, and no output schema, the description is moderately complete. It explains what the tool does and what it returns, but lacks context on when to use it, error handling, or how it fits with siblings. For a zero-param tool, this is adequate but has gaps.

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 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for zero-parameter tools. No additional parameter information is required or provided.

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: 'Verify the index is ready and report status.' This is a specific verb ('verify' + 'report') with a clear resource ('the index'). However, it doesn't explicitly differentiate from sibling tools like 'update_repository' or 'list_versions' that might also relate to system status.

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 prerequisites, timing (e.g., after updates), or how it differs from other status-related tools in the sibling list. The agent must infer usage from the purpose alone.

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/hackIDLE/fedramp-docs-mcp'

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