Skip to main content
Glama
Sign In

uCAD

by app.ucad
OverviewDiscussionsAdmin

Look at a drawing

view
Read-onlyIdempotent

Pictures of a drawing as it is now (with anything the user changed by hand), from the sides asked for.

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

Input Schema

NameRequiredDescriptionDefault
viewsNoThe sides to show it from (one picture each): iso, iso_back, front, back, left, right, top, bottom. Default: iso.
widthNoPicture width in pixels (default 800)
heightNoPicture height in pixels (default 600)
drawingNoThe drawing's id (from an earlier run_script, or from drawings). Left out: the drawing worked on last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the description's job is to add nuance — and it does: it discloses the return type is pictures and that the render reflects the current edited state rather than the original script output. It still doesn't say how multiple views are returned or whether the drawing must exist in the session.

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?

A single tight sentence with no filler; the state-semantics parenthetical is well placed. The phrasing is slightly awkward ('Pictures of a drawing ... from the sides asked for') and would read better with an active verb.

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?

With all parameters optional, fully documented in the schema, and annotations covering the safety profile, the remaining burden is small — and the description addresses the two non-obvious points: output is images and they reflect live edits. Minor gaps around multi-view return format and drawing-resolution behavior keep it from being complete.

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 coverage is 100%, with enums, defaults, and size limits all documented in the schema, so the baseline is 3. The phrase 'from the sides asked for' merely re-references the views parameter without adding any format or ordering detail.

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 sentence states the resource (a drawing) and the output (pictures rendered from the requested sides), and adds a scope nuance: it reflects the drawing 'as it is now,' including manual edits. It lacks an explicit action verb ('Render'/'Capture') and never names a sibling, so it is clear but not sharply differentiated from tools like drawings or run_script.

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?

There is no explicit when-to-use guidance, no preconditions, and no mention of alternatives such as run_script (to modify) or drawings (to list ids). The agent must infer that this is the tool for visually inspecting a drawing.

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

All uCAD toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources