Skip to main content
Glama
Sign In
sketchflow-mcp

sketchflow-mcp

by 4Ship-ca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

model_view

Generates a PNG of linked top, 3D, front, and right views with dimensions and dashed hidden edges, plus a model summary, then restores the user's view.

Instructions

See the 3D model: returns a PNG of the linked views (default all four: TOP top-left, 3D top-right, FRONT bottom-left, RIGHT bottom-right, third-angle) with carried dimensions and dashed hidden edges, plus the model summary. The user's own view is restored afterwards.

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

Input Schema

NameRequiredDescriptionDefault
keepNoleave the user's screen on this view (default false)
viewNodirection of the 3D pane camera
jointsNoshow a motion pose without changing the model: {jointId: value} or {jointId: {angle: 30, travel: 10}}
layoutNodefault 4
sectionNocut the model with a plane (offset from the origin); cut faces show hatched
dimensionsNo
hidden_linesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-beta.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does substantial work: it discloses the output type (PNG), exact default layout and quadrant placement, third-angle convention, dimension carry-over, dashed hidden edges, and the extra model summary. It also discloses a side effect and its mitigation — the user's view is restored afterwards — which is exactly the kind of behavior an agent cannot infer from the schema.

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 front-loaded sentence that leads with the verb and the artifact, then packs the layout defaults, rendering conventions, and side-effect note. The nested parentheses make one clause hard to parse, but no sentence is wasted.

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?

Seven optional parameters, nested objects, no output schema, and no annotations set a high bar, and the description covers the return artifact, the default layout, and the temporary screen mutation. Remaining gaps are minor: it does not say which model/session is rendered or whether dimensions/hidden edges default on.

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 a reasonably high 71%, so most parameters are already documented, and the description adds meaning for a few of them: it spells out the default quad layout, explains the screen-restoration behavior that gives 'keep' its purpose, and confirms dimensions/hidden edges are rendered. It leaves the section plane and joints pose semantics entirely to the schema text, so it does not clearly exceed the baseline.

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?

Opens with a specific verb+resource ('See the 3D model') and immediately names the artifact returned (a PNG of linked views plus the model summary), so an agent knows this is a render/preview tool rather than a data query. It does not explicitly contrast itself with nearby siblings like model_query, model_describe, or model_export, which keeps it short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by 'See the 3D model' and the default four-view render, which is enough for an agent to know this is the visual-inspection path. However, no alternative is named and no condition is given for choosing between this, model_query, or model_export, and there is no when-not guidance.

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