Skip to main content
Glama
Sign In
kompas3d

kompas3d

by hymaxo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

draw_circle

Create a native editable circle in a KOMPAS drawing or fragment view by specifying center coordinates, radius in millimeters, and optional style and view settings.

Instructions

Draw a native editable circle in a drawing/fragment view; radius in mm.

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": {
      "drawing_handle": "<drawing_handle>",
      "x": "<x>",
      "y": "<y>",
      "radius": "<radius>"
    },
    "name": "draw_circle"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
styleNo
radiusYes
view_numberNo
drawing_handleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the circle is 'native editable' and that radius uses mm, but it does not state requirements like an existing drawing_handle, coordinate-system behavior, side effects, or error cases.

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?

A single front-loaded sentence conveys the core action and scope with no filler. The useful unit detail earns its place at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with six parameters, four required, no annotations, and no output schema, this description is too sparse to give an agent a complete calling context. It does not explain what drawing_handle refers to, how style or view_number behave, or in what units x and y are expressed.

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 description coverage is 0%, so the description must compensate. It adds meaning for radius (mm) and implicitly places x/y in a drawing view, but it leaves drawing_handle, style, view_number, and x/y units undefined.

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 clearly states a specific action ('Draw'), a distinct resource ('native editable circle'), and the context ('in a drawing/fragment view'). It could explicitly contrast with sibling drawing tools like draw_line, but the resource is specific enough to tell the tools apart.

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?

The phrase 'in a drawing/fragment view' implies when the tool applies, but there is no explicit guidance about when to choose it over alternatives or when not to use it. No exclusions or preconditions are stated.

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