Skip to main content
Glama

draw_xline

Create an infinite construction line in CAD by specifying a base point and angle. Use it for precise alignment and reference geometry.

Instructions

Infinite construction line through (x,y) at angle degrees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes
angleNo
layerNoCOSTRUZIONE

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It does mention the infinite nature and the geometric parameters, but it omits that this creates a new drawing entity and the default layer behavior. No contradiction with annotations exists.

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?

The description is a single, front-loaded sentence with no filler. Every word adds meaning: 'infinite' conveys the line type, 'through (x,y)' indicates the anchor point, and 'at angle degrees' specifies the orientation.

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

Completeness3/5

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

The tool is simple and an output schema exists, but the description fails to provide usage context or note the default layer (COSTRUZIONE). It covers the core geometry but leaves out practical details an agent would need, such as layer handling and comparison to draw_line.

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 description coverage is 0%, so the description must compensate. It clearly explains x,y as a point and angle in degrees, mapping well to three of the four parameters. The layer parameter is not explained, but it's optional with a default.

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 explicitly states the tool draws an 'Infinite construction line' through a point at an angle, which clearly distinguishes it from finite lines like draw_line. The verb is implied by the tool name, and the resource is precisely described.

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?

No explicit when-to-use guidance or comparison to alternatives is provided. The term 'construction line' hints at a purpose, but there is no mention of when to choose this over draw_line or other drawing tools.

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/Psalmustrack/lambdacad-mcp'

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