Skip to main content
Glama

Render link

render_link

One link that renders up to 20 of your drawings as files, each with its own choices (format, resolution, aspect, background, hand…; see get_drawing export_options). Opening it in a browser renders them one after another and saves each file to that browser’s downloads; drawings still being drawn are rendered once they finish. Follow it with wait_render.

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": {
      "drawings": "<drawings>"
    },
    "name": "render_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
drawingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false; the description adds substantial context the agent could not infer — rendering happens in a browser, files land in the browser's downloads folder, drawings are processed sequentially, and in-progress drawings are rendered once finished. It omits link expiry/lifetime and any auth requirements, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the core capability and then the browser/download mechanics and follow-up. The parenthetical option list is efficient, though the sentence runs long and mixes capability with cross-references.

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?

Given a single nested array parameter, no output schema, and sparse annotations, the description supplies the missing workflow (open link in browser, then wait_render) and the capacity limit of 20. A brief note on what the tool returns (a URL) and its lifetime would make it fully self-contained.

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 0%, so the description has to carry meaning, and it does partially: it enumerates format, resolution, aspect, background, hand and delegates the rest to get_drawing export_options. It does not explain per-drawing nesting behavior (e.g. skip, trace, timing, hand_tilt) beyond the trailing ellipsis, leaving several properties undocumented anywhere.

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

Purpose5/5

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

The description states a specific verb+resource with scope: it produces one link that renders up to 20 drawings as files, each with independent export choices. This distinguishes it from wait_render, which is explicitly named as the follow-up rather than an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent the correct sequence ('Follow it with wait_render') and points to get_drawing export_options for option semantics. It does not state when to prefer this over any other rendering path, but the workflow guidance is concrete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.