Skip to main content
Glama

Add Thumbnail

add_thumbnail

Places a small pinned isometric pictorial view in a drawing sheet’s top-right corner only when it fits without crowding existing views or dimensions; call after views, dimensions, and fit_page.

Instructions

Place a small isometric pictorial (vector TechDraw view) in the sheet's top-right corner IF it fits without crowding existing views/dimensions. It is pinned there, never dimensioned, and ignored by drawing_gate. Call it AFTER views, dimensions and fit_page.

Returns {placed, box, scale?, view?, reason?}; placed=False with a reason when the corner is occupied.

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": {
      "page": "<page>"
    },
    "name": "add_thumbnail"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoIsoThumb
pageYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: states the thumbnail is pinned, never dimensioned, and ignored by drawing_gate — non-obvious behavior that affects downstream gate calls. It also documents the failure mode (placed=False with reason when the corner is occupied), which the annotation hints cannot convey.

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?

Three dense sentences: placement constraint first, behavioral contract next, return shape last. No filler, and the most actionable constraint (ordering) is front-loaded.

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?

No output schema, but the description enumerates the return fields (placed, box, scale?, view?, reason?) and the failure semantics, so an agent can interpret results. The remaining gap is documentation of the 'page' and 'name' parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (only 'workspace' is described), and the description never explains 'page' or 'name' beyond the general notion of a sheet. With two undocumented parameters and no compensating detail, it falls below the baseline-3 case.

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?

A specific verb (place) applied to a concrete resource (small isometric pictorial / vector TechDraw view) with exact placement scope (sheet's top-right corner). It is trivially distinguishable from siblings like add_projection_group or render_view.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('IF it fits without crowding existing views/dimensions') and a hard ordering rule ('Call it AFTER views, dimensions and fit_page'). An agent knows both when to call it and when the call is premature.

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