Skip to main content
Glama

create_counterbore_hole

Generates a counterbore hole sized for JIS socket head cap screws, automatically using the correct head diameter and depth for M2 through M12 bolts.

Instructions

Create a counterbore hole sized for a JIS socket head cap screw (B1176). Automatically uses correct head diameter and depth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sizeYesBolt size: M2 through M12.
hole_depthYesThrough-hole depth in mm. Use 0 for through-all.
xNoHole center X position in mm
yNoHole center Y position in mm
body_nameNoTarget body name.
face_indexNoFace index for hole placement.
Behavior2/5

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

With no annotations, the description carries full burden. It mentions automatic sizing but does not disclose side effects (e.g., body modification), required context, or error conditions.

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?

Two sentences, front-loaded with purpose and key behavioral trait (automatic sizing). No wasted words.

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?

Given no output schema, the description provides the core purpose and key automation, but lacks detail on return value, error states, or which parameters are optional when body is selected.

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?

All 6 parameters have schema descriptions (100% coverage), so baseline is 3. The description adds 'automatic head diameter and depth' but does not enhance understanding of individual parameters beyond the schema.

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 tool creates a counterbore hole specifically for JIS socket head cap screws, with automatic sizing. This distinguishes it from siblings like create_countersink_hole and create_threaded_hole.

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 description implies use for JIS counterbore holes but does not explicitly state when to use this tool versus alternatives. No guidance on prerequisites or when not to use it.

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/mikan-atomoki/text-to-model'

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