Skip to main content
Glama

List Hole Thread Options

list_thread_options

List valid coupled thread type and size values for threaded holes, optionally filtered by type, before creating a hole to prevent failed enum-value calls.

Instructions

Discover the COUPLED ThreadType / ThreadSize enums on the hole tool.

Call with no args to list valid thread_type values. Call with thread_type=... to list the valid thread_size values for that type (the coupling: thread_size='M4' is valid for 'ISOMetricProfile' but not for 'UNC'). Use this BEFORE calling hole(threaded=True, thread_type=..., thread_size=...) to avoid a failed enum-value call.

Returns either {thread_types: [...]} or {thread_type, thread_sizes: [...]}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_thread_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoRun this call in this named workspace
thread_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Discloses behavior beyond the annotations: the enum coupling rule (M4 valid for ISOMetricProfile but not UNC) and both possible return shapes. Note the annotations declare readOnlyHint=false even though the description describes a pure discovery/list operation — an under-claim rather than a dangerous over-claim, so no contradiction flag, but it is worth knowing the server is not asserting read-only here.

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?

Front-loaded with the one-line purpose, then the two call modes, then the pre-call rationale, then return shapes. Every line adds information an agent would otherwise have to discover by trial and error; nothing is redundant.

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

Completeness5/5

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

There is no output schema, and the description supplies both possible return shapes ({thread_types: [...]} or {thread_type, thread_sizes: [...]}), plus the failure mode it prevents. For a two-optional-param lookup tool, nothing material is missing.

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 coverage is 50%, and the description compensates well for the undocumented `thread_type` param: it explains what the value selects and what the response becomes. The `workspace` param is not mentioned in the description at all, relying entirely on its schema description, which keeps this short of a 5.

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?

States a specific verb ('Discover', 'list') and an exactly-scoped resource: the COUPLED ThreadType/ThreadSize enums on the hole tool. It also implicitly separates itself from the `hole` sibling by being the pre-flight enum lookup that `hole` consumes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the precise call protocol: no args lists valid thread_type values; thread_type=... lists the coupled thread_size values. It also states the ordering constraint explicitly ('Use this BEFORE calling hole(threaded=True, ...) to avoid a failed enum-value call'), which is exactly the when-to-use guidance an agent needs.

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