Skip to main content
Glama
cloudcwfranck

@cloudcraftwithfranck/govcloud-mcp

gcc_high_guidance

Identify Azure GCC High configuration requirements, limitations, and gotchas for any service or scenario, including differences from Azure Government and Commercial.

Instructions

Get Azure GCC High specific configuration requirements, limitations, and gotchas for any Azure service or scenario. Includes what works differently in GCC High vs Azure Government vs Commercial.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesAzure service name or scenario
scenarioNoWhat you are trying to accomplish (optional)

Implementation Reference

  • The main handler function that executes the gcc_high_guidance tool logic. Validates args via Zod schema, then sends a prompt to Anthropic Claude with GCC High-specific system instructions covering DoD/Azure GCC High differences, limitations, workarounds, and undocumented behaviors.
    export async function handleGccHigh(args: unknown): Promise<string> {
      return runTool('gcc_high_guidance', args, Schema, async ({ service, scenario }) => {
        const response = await anthropic.messages.create({
          model: MODEL,
          max_tokens: getTokenBudget('gcc_high_guidance'),
          system: GCC_SYSTEM,
          messages: [
            {
              role: 'user',
              content: `Provide complete GCC High guidance for: **${service}**
    ${scenario ? `\nScenario: ${scenario}` : ''}
    
    Focus on what's different, what's broken, what's undocumented, and what every GCC High engineer needs to know before they spend days debugging something that should have been a 5-minute warning.`,
            },
          ],
        });
    
        return response.content[0].type === 'text' ? response.content[0].text : '';
      });
    }
  • Zod input schema defining required 'service' (string, max 500) and optional 'scenario' (string, max 500) parameters for the tool.
    const Schema = z.object({
      service: z.string().max(500),
      scenario: z.string().max(500).optional(),
    });
  • Tool registration object with name 'gcc_high_guidance', description, and JSON input schema. Exported and included in the allTools array in src/tools/index.ts.
    export const gccHighTool = {
      name: 'gcc_high_guidance',
      description:
        'Get Azure GCC High specific configuration requirements, limitations, and gotchas for any Azure service or scenario. Includes what works differently in GCC High vs Azure Government vs Commercial.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          service: { type: 'string', description: 'Azure service name or scenario' },
          scenario: { type: 'string', description: 'What you are trying to accomplish (optional)' },
        },
        required: ['service'],
      },
    };
  • Switch-case dispatch in handleToolCall routing the name 'gcc_high_guidance' to the handleGccHigh handler function.
    export async function handleToolCall(name: string, args: unknown): Promise<string> {
      switch (name) {
        case 'bicep_analyze':         return handleBicepAnalyze(args);
        case 'bicep_remediate':       return handleBicepRemediate(args);
        case 'control_lookup':        return handleControlLookup(args);
        case 'control_narrative':     return handleControlNarrative(args);
        case 'poam_generate':         return handlePoamGenerate(args);
        case 'ato_readiness':         return handleAtoReadiness(args);
        case 'oscal_fragment':        return handleOscalFragment(args);
        case 'landing_zone_design':   return handleLandingZone(args);
        case 'landing_zone_reference': return handleLandingZoneReference(args);
        case 'azure_service_selector': return handleServiceSelect(args);
        case 'gcc_high_guidance':     return handleGccHigh(args);
        case 'private_endpoint_map':  return handlePrivateEndpoint(args);
        case 'bigbang_validate':      return handleBigbangValidate(args);
        case 'bigbang_harden':        return handleBigbangHarden(args);
        case 'ironbank_lookup':       return handleIronbankLookup(args);
        case 'addon_configurator':    return handleAddonConfigurator(args);
        case 'pipeline_audit':        return handlePipelineAudit(args);
        case 'signing_config':        return handleSigningConfig(args);
        case 'devsecops_scorecard':   return handleDevsecopsScorecard(args);
        case 'ssp_section':           return handleSspSection(args);
        case 'contingency_plan':      return handleContingencyPlan(args);
        case 'govcloud_quickstart':   return handleGovcloudQuickstart(args);
        default:
          throw new Error(`Unknown tool: ${name}`);
      }
    }
  • Token budget configuration for gcc_high_guidance: 2048 max_tokens. Also timeout of 20000ms (line 38). Used by getTokenBudget() in the handler.
    gcc_high_guidance: 2048,
Behavior4/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 describes a read-only retrieval operation ('Get') with no destructive hints, which is transparent. It could add more detail about response format or behavior, but it's adequate.

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 two sentences that efficiently convey purpose and scope with no filler. It is front-loaded with the main action and then adds comparative context.

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?

For a simple guidance retrieval tool with no output schema, the description fully explains its purpose, scope, and comparative value. It could optionally mention typical use cases, but it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description essentially repeats the schema's parameter descriptions ('Azure service name or scenario', 'What you are trying to accomplish'). It adds no additional meaning beyond what the schema provides, meeting the baseline.

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 it retrieves GCC High specific configuration requirements, limitations, and gotchas for any Azure service or scenario. It distinguishes itself from siblings like 'govcloud_quickstart' by specifying the GCC High context.

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 use when needing GCC High specifics, and includes comparisons to Azure Government and Commercial. However, it does not explicitly state when not to use it or mention alternatives among the many sibling tools.

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