Skip to main content
Glama
Sign In
mcp-azure

mcp-azure

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get resource

get_resource
Read-onlyIdempotent

Fetch an Azure resource by its full ARM ID and supply the required api-version to retrieve its details.

Instructions

Fetch a resource by its full ARM id. Provide the api-version for the resource type.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resourceId": "<resourceId>",
      "apiVersion": "<apiVersion>"
    },
    "name": "get_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiVersionYesAPI version for this resource type, e.g. 2023-07-01
resourceIdYesFull ARM resource id (/subscriptions/…/providers/…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only that an API version must be supplied, which is prerequisite-flavored but reveals nothing about auth, throttling, or return shape; with annotations doing the heavy lifting, this is adequate but minimal.

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?

Two short sentences, front-loaded with the core action and its key input. No filler or redundancy; every clause earns its place.

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 read-only fetch of a single resource, the description plus rich annotations are nearly sufficient. Since no output schema exists, one might expect a brief note on what is returned, but the tool's nature makes that largely inferable.

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 description coverage is 100%, with both params documented (full ARM id format, API version example), so the schema already carries the semantics. The description restates the same two inputs without adding format, syntax, or validation detail beyond the schema, making the baseline 3 correct.

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?

States a specific verb and resource ('Fetch a resource by its full ARM id'), which contrasts naturally with the list_* siblings. It clearly distinguishes single-resource retrieval from enumeration, though it does not explicitly name an alternative sibling.

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 only usage-adjacent sentence ('Provide the api-version for the resource type') is a parameter instruction rather than guidance on when to use this tool. There is no mention of when to prefer it over list_resources or any prerequisite/exclusion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools