Skip to main content
Glama
zinin

sketchup-mcp2

by zinin

fillet_edge

Round edges of a group or component with a specified radius and arc segments. Returns stats on successful fillets and failed cuts.

Instructions

Round (fillet) edges of a group/component by radius mm with segments arc segments.

By default ALL edges are filleted. Unreliable on non-manifold geometry.

Returns: JSON {id, name, type, bbox_mm|null, edges_filleted, stats{attempted, skipped_no_match, subtract_failed, succeeded}} — check stats.subtract_failed == 0 (failed cuts) and stats.skipped_no_match == 0 (edges consumed by earlier cuts).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEntity ID from a previous response (integer or its string form)
radiusNoFillet radius in mm
segmentsNoArc segments per rounded edge

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the unreliability on non-manifold geometry, explains the return JSON structure, and advises checking specific stats fields. It could mention that the operation modifies geometry destructively but is implied.

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 concise with three sentences plus a bullet of return info. It front-loads the main action. Could be slightly more streamlined, but no significant waste.

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 the presence of an output schema and 3 parameters, the description covers purpose, default behavior, non-manifold warning, and return interpretation. It is fairly complete for the tool's complexity.

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%, so baseline is 3. The description adds value by explaining default behavior and return stats, but the parameter descriptions in the schema are already clear. The description does not provide additional semantics beyond the schema for the parameters.

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 clearly states the action ('Round (fillet) edges of a group/component') and distinguishes from sibling tool 'chamfer_edge' by specifying 'Round' vs bevel. It also mentions the parameters 'radius' and 'segments' directly.

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?

The description provides context on default behavior ('By default ALL edges are filleted') and warns about non-manifold geometry. However, it does not explicitly contrast with chamfer_edge or specify when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zinin/sketchup-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server