Skip to main content
Glama
U-C4N
by U-C4N

Gear: Spur Front View

gear_draw_spur_front_view

Draw a deterministic spur gear front view with specified module and teeth. Optionally add keyway, bore, and set pressure angle.

Instructions

Deterministic spur gear front view (no helix symbol).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teethYes
moduleYes
center_xNo
center_yNo
keyway_depthNo
keyway_widthNo
bore_diameterNo
pressure_angleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations only indicate destructiveHint=false. The description adds 'Deterministic', implying reproducible output, but fails to disclose that the tool likely creates entities in the drawing or its side effects. Given limited annotations, the description adds marginal value.

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 a single short sentence, concise and front-loaded. However, it is so minimal that it sacrifices informativeness, though this is a matter of trade-off rather than poor structure.

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?

Given the tool's complexity (8 parameters, 2 required) and sibling tools, the description is insufficient. It does not explain that the tool generates a gear shape in the drawing, how parameters affect the result, or that an output schema exists. The agent lacks critical context for correct usage.

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

Parameters1/5

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

Schema description coverage is 0%, placing full burden on the description to explain parameters. The description does not mention any of the 8 parameters (module, teeth, pressure_angle, etc.), leaving the agent without guidance on how to specify a valid gear.

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 states 'spur gear front view' which clearly identifies the tool's output. The phrase 'no helix symbol' differentiates from the helical gear sibling tool, but the lack of an explicit verb like 'draw' or 'create' slightly reduces clarity.

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 explicitly excludes helical gears with 'no helix symbol', which helps the agent choose between this and the helical sibling. However, it does not provide guidance on when to use this tool versus other drawing tools or any prerequisites.

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/U-C4N/Autocad-MCP'

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