Skip to main content
Glama
dhippley

Azure Topology Graph MCP Server

by dhippley

get_resource

Retrieve detailed information about a specific Azure resource using its full resource ID to analyze infrastructure components.

Instructions

Get detailed information about a specific Azure resource

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resourceIdYesFull Azure resource ID

Implementation Reference

  • src/server.ts:357-370 (registration)
    Registration of the 'get_resource' tool in the ListTools response, including name, description, and input schema definition.
    {
      name: 'get_resource',
      description: 'Get detailed information about a specific Azure resource',
      inputSchema: {
        type: 'object',
        properties: {
          resourceId: {
            type: 'string',
            description: 'Full Azure resource ID',
          },
        },
        required: ['resourceId'],
      },
    },
  • Handler implementation for the 'get_resource' tool. It fetches the topology, finds the resource by ID, and returns formatted details including name, type, group, location, subscription, ID, tags, and properties.
    case 'get_resource': {
      const { resourceId } = args as { resourceId: string };
      const topology = await buildTopology();
      const resource = topology.nodes.find(n => n.id === resourceId);
      
      if (!resource) {
        throw new McpError(ErrorCode.InvalidRequest, `Resource not found: ${resourceId}`);
      }
      
      return {
        content: [
          {
            type: 'text',
            text: `Resource Details:\n\n` +
              `Name: ${resource.name}\n` +
              `Type: ${resource.type}\n` +
              `Resource Group: ${resource.resourceGroup}\n` +
              `Location: ${resource.location}\n` +
              `Subscription: ${resource.subscriptionId}\n` +
              `ID: ${resource.id}\n\n` +
              (resource.tags ? `Tags: ${JSON.stringify(resource.tags, null, 2)}\n\n` : '') +
              (resource.properties ? `Properties: ${JSON.stringify(resource.properties, null, 2)}` : ''),
          },
        ],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves 'detailed information,' implying a read-only operation, but doesn't specify authentication needs, rate limits, error conditions, or what 'detailed' entails (e.g., metadata, configuration, status). This leaves significant gaps for a tool interacting with Azure resources.

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 no wasted words. It's front-loaded with the core purpose ('Get detailed information about a specific Azure resource'), making it easy to parse quickly. Every word earns its place, achieving optimal conciseness.

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 moderate complexity (interacting with Azure resources), lack of annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, and output format. This leaves the agent with gaps, especially for error handling or result interpretation, making it just viable but not fully informative.

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?

The input schema has 100% description coverage, with the parameter 'resourceId' documented as 'Full Azure resource ID.' The description adds minimal value beyond this, only implying the parameter identifies a 'specific Azure resource.' Since the schema does the heavy lifting, the baseline score of 3 is appropriate, as the description doesn't provide additional syntax or format details.

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 with a specific verb ('Get') and resource ('Azure resource'), and specifies it retrieves 'detailed information' rather than just basic data. However, it doesn't differentiate from sibling tools like 'search_resources' or 'get_neighbors' that might also retrieve Azure resource information, preventing a perfect score.

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 like 'search_resources' (which might list multiple resources) or 'get_neighbors' (which might retrieve related resources). It mentions 'specific Azure resource' but doesn't clarify prerequisites, such as needing a full resource ID versus a name, or when other tools might be more appropriate.

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