Skip to main content
Glama
sketchflow-mcp

sketchflow-mcp

by 4Ship-ca

model_query

Queries read-only 3D model geometry to return faces, edges, distance and angle measurements, section areas, bounding boxes, and connector positions.

Instructions

Ask the model about its geometry (read-only). what: "faces" (every face of a part — or of all parts — with the connector name to target it by (top, slope, face:side2…), owner, normal, centre and area; curved surfaces listed as such), "edges" (sharp edges of a part with end points and lengths), "measure" (from / to: {obj, conn} or [x,y,z]: distance, dx/dy/dz, and the angle between two face normals), "section" (axis x|y|z, offset: the cut area through the model there, per part), "bbox" (overall and per part), "connectors" (id: every connector with position and normal). Coordinates are mm from the model origin.

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_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
toNo
axisNo
fromNo
whatNo
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-beta.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; it does state the operation is read-only and documents the return content for each mode, plus units in millimetres. It omits important behavior such as what 'limit' does, whether results are paginated, permission requirements, and error behavior, so it does not fully compensate for the missing annotations.

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?

The description is front-loaded with the read-only nature and the query selector, then compactly enumerates each mode. It is dense with parentheticals but every sentence conveys relevant semantics; the long run-on structure slightly reduces parseability.

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?

For a seven-parameter geometry query with no annotations and no output schema, the description covers modes, return fields, coordinate units, and the read-only guarantee. Remaining gaps are the undocumented 'limit' parameter and the lack of sibling differentiation, which are minor but real for its complexity.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry parameter meaning, and it largely does: 'what' enum values are defined, 'axis' and 'offset' are explained under section, 'from'/'to' accept {obj, conn} or [x,y,z], and 'id' is tied to the connectors mode. The 'limit' parameter is never mentioned, leaving one of seven parameters undocumented.

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 description names a specific verb and resource (query model geometry) and enumerates the six query modes, so an agent knows exactly what the tool does. It does not differentiate from siblings such as model_describe, model_view, or model_check, leaving an agent to infer which geometry-query surface to choose.

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?

Each 'what' value is paired with an explanation of what it returns, which implicitly guides selection among modes. However, there is no explicit when-to-use, when-not-to-use, or named alternative such as model_view for visual inspection, so the guidance is implied rather than spelled out.

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