Skip to main content
Glama
Sign In
ArchScript MCP

ArchScript MCP

by schlummer13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Render the diagram

render_diagram
Read-only

Render a document’s architecture diagram as a PNG image from its last valid state; omit the document to target the frontmost one.

Instructions

The document's diagram as a PNG image (the last valid state).

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": "render_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNoDocument id (e.g. doc1), file name or project name. Omit for the frontmost document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

The description adds valuable behavioral context by specifying that it returns 'the last valid state,' which is a critical detail regarding versioning and stability. This adds context beyond the simple read-only annotation.

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 extremely concise, delivering the core functionality in a single, direct sentence without unnecessary padding or jargon.

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 simple input schema and the lack of an output schema, the description is sufficient to tell the agent what output to expect (a PNG image). It is adequate but does not provide deep operational context.

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?

Since schema coverage is 100%, the description does not need to elaborate on parameter meaning. It provides slight confirmation that omitting the document ID targets the frontmost document, which is consistent with the schema but not functionally critical.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The purpose is clear—to generate a PNG of the document's diagram. However, it is not strongly differentiated from other image export siblings, like 'export' or 'get_document', making the exact scope slightly ambiguous to an AI agent.

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 definition provides no guidance on when to use this tool versus alternatives that might achieve a similar output. It lacks necessary constraints or 'when not to use' information.

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