Skip to main content
Glama
dhippley

Azure Topology Graph MCP Server

by dhippley

refresh_topology

Update Azure infrastructure topology maps by re-querying Azure Resource Graph, ARM, and Network Watcher APIs to reflect current resource states and relationships.

Instructions

Refresh the topology cache by re-querying Azure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the refresh_topology tool. Invalidates the cache and rebuilds the topology graph from Azure resources, returning a success message with node and edge counts.
    case 'refresh_topology': {
      topologyCache = null;
      cacheTimestamp = 0;
      const topology = await buildTopology();
      
      return {
        content: [
          {
            type: 'text',
            text: `Topology refreshed successfully.\n\n` +
              `Resources: ${topology.nodes.length}\n` +
              `Connections: ${topology.edges.length}`,
          },
        ],
      };
    }
  • src/server.ts:418-425 (registration)
    Tool registration in the ListToolsRequestHandler, defining the tool's name, description, and input schema (no parameters required).
    {
      name: 'refresh_topology',
      description: 'Refresh the topology cache by re-querying Azure',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the refresh_topology tool, specifying an empty object (no input parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a read/write operation, its impact (e.g., performance, data freshness), rate limits, or permissions required, leaving significant gaps.

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, efficient sentence with zero waste—it directly states the purpose without redundancy. It's appropriately sized for a no-parameter tool and front-loaded with essential information.

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?

For a tool with 0 parameters and no output schema, the description is minimally adequate but lacks completeness. It doesn't explain what 'topology cache' entails, the outcome of refreshing, or error handling, leaving the agent with insufficient context for optimal 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?

The tool has 0 parameters with 100% schema coverage, so no parameter documentation is needed. The description adds value by explaining the action involves 're-querying Azure', which provides context beyond the empty schema, justifying a baseline above 3.

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 action ('refresh') and the resource ('topology cache'), specifying it's done by 're-querying Azure'. This distinguishes it from siblings like 'export_topology' or 'search_resources', though it doesn't explicitly contrast them.

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 like 'get_resource' or 'search_resources'. It implies usage when the cache needs updating but offers no explicit context, prerequisites, or exclusions.

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/dhippley/azure_mcp_graph'

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