Skip to main content
Glama
cloudcwfranck

@cloudcraftwithfranck/govcloud-mcp

govcloud_quickstart

Verify MCP server status and retrieve top example prompts for all tool categories after installation.

Instructions

Confirm the GovCloud MCP server is running correctly and get the top example prompts for every tool category — the ideal first call after installation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler function for the 'govcloud_quickstart' tool. Returns a predefined markdown response confirming the server is running and listing top prompts and tool categories.
    export function handleGovcloudQuickstart(_args: unknown): Promise<string> {
      return Promise.resolve(QUICKSTART_RESPONSE);
    }
  • Tool definition object including name, description, and empty inputSchema (no parameters required).
    export const govcloudQuickstartTool = {
      name: 'govcloud_quickstart',
      description:
        "Confirm the GovCloud MCP server is running correctly and get the top example prompts for every tool category — the ideal first call after installation.",
      inputSchema: {
        type: 'object' as const,
        properties: {},
        required: [],
      },
    };
  • Import of govcloudQuickstartTool and handleGovcloudQuickstart, inclusion in allTools array, and routing in handleToolCall switch for 'govcloud_quickstart'.
    import { govcloudQuickstartTool, handleGovcloudQuickstart } from './govcloud-quickstart.js';
    
    export const allTools = [
      // Compliance
      bicepAnalyzeTool,
      bicepRemediateTool,
      controlLookupTool,
      controlNarrativeTool,
      poamGenerateTool,
      atoReadinessTool,
      oscalFragmentTool,
      // Architecture
      landingZoneTool,
      landingZoneReferenceTool,
      serviceSelectTool,
      gccHighTool,
      privateEndpointTool,
      // Platform One
      bigbangValidateTool,
      bigbangHardenTool,
      ironbankLookupTool,
      addonConfiguratorTool,
      // Pipeline
      pipelineAuditTool,
      signingConfigTool,
      devsecopsScoreCardTool,
      // Documents
      sspSectionTool,
      contingencyPlanTool,
      // Meta
      govcloudQuickstartTool,
  • Token budget (1024) and timeout (5000ms) configuration for the govcloud_quickstart tool.
    govcloud_quickstart: 1024,
    bicep_analyze: 4096,
  • Minimum response length validation (200 characters) for govcloud_quickstart.
      govcloud_quickstart: 200,
    };
Behavior3/5

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

No annotations provided, so the description carries the burden. It mentions checking server status and getting prompts, implying a read-only operation, but doesn't detail behavior like side effects, output format, or error states.

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?

Single sentence with all key information front-loaded: action (confirm/get), purpose (server check + example prompts), and usage context (first call). Zero waste.

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 health/intro tool with no params and no output schema, the description is complete enough. It explains what, why, and when to use.

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?

No parameters exist (schema is empty, 100% coverage). Baseline for 0 params is 4; description adds no param info, but none is needed.

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's purpose: confirm server is running and get top example prompts per category. It uses specific verbs 'confirm' and 'get' and distinguishes from siblings as a quickstart/intro tool.

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?

Explicitly says 'the ideal first call after installation,' providing clear when-to-use context. No when-not-to-use or alternatives, but the context strongly implies it's a starter tool.

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/cloudcwfranck/govcloud-mcp'

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