Skip to main content
Glama
Sign In
Azure Diagram MCP Server

Azure Diagram MCP Server

by Jah-yee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_diagram_examples

Retrieves example diagram code for Azure, sequence, flow, class, K8s, on-prem, or custom diagrams to help you get started with infrastructure diagram generation.

Instructions

Get example diagram code for the specified diagram type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_diagram_examples"
  }
}

Input Schema

NameRequiredDescriptionDefault
diagram_typeNoThe type of diagram examples to retrieve. Options: azure, sequence, flow, class, k8s, onprem, custom, all.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description bears full responsibility. It indicates a read operation ('Get'), but lacks details on safety, idempotency, or error behavior. Minimal transparency.

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, front-loaded sentence with no extraneous words. Every word serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should clarify return format. It only says 'example diagram code' without specifying structure, completeness, or example nature.

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 already describes the parameter with 100% coverage. The description adds no extra semantic value beyond referencing the type.

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 retrieves example diagram code for a specified type. It distinguishes from siblings like generate_diagram (which creates) and list_icons (which lists icons), but does not explicitly differentiate.

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 on when to use this tool versus alternatives, nor any exclusions or contextual hints. The agent is left without context for decision-making.

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