Skip to main content
Glama

Add Feature Note

add_feature_note

Attach a manufacturing note to an enumerated curved or periodic feature, letting drawing_gate record complex profiles, tooth patterns, or cone angles as covered.

Instructions

Attach an explicit manufacturing NOTE that satisfies a curved/periodic feature the drawing_gate enumerates (issue #108) — the 'per CAD model / profile table' coverage for geometry a single number can't capture (a freeform/BSpline wall's profile, a tooth pattern's full parameter set) or a documented cone angle. feature is the enumerated feature id (e.g. 'FREEFORM1', 'PAT1', 'CONE1', from drawing_gate's enumerated_features); text defaults to a sensible callout. The gate reads the note back as coverage. Returns {handle, name, feature, text}.

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": {
      "page": "<page>",
      "feature": "<feature>"
    },
    "name": "add_feature_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
kindNofeature
nameNoFeatureNote
pageYes
textNo
featureYes
workspaceNoRun this call in this named workspace

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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered; the description adds genuinely non-obvious context that the note is consumed by drawing_gate as coverage and states the return shape {handle, name, feature, text}. It does not say what happens if a note already exists on the feature or whether the call is idempotent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The verb and resource are front-loaded and the paragraph is bounded, but it carries noise: the '(issue #108)' tracker reference earns nothing for an agent, and the drawing_gate enumeration relationship is stated twice. Dense parenthetical stacking slows parsing of an otherwise short description.

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 workflow dependency on drawing_gate is well explained and the return values are given despite no output schema. Nevertheless the required `page` argument and placement (x/y) semantics are nowhere defined, which matters for an 8-parameter tool sitting in a very large sibling set of drawing/annotation tools.

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?

Schema coverage is only 13%, so the description must compensate and does so for the two most domain-specific parameters: `feature` is defined as the enumerated id with examples from drawing_gate's enumerated_features, and `text` is described as defaulting to a sensible callout. But the required `page` parameter has no explanation anywhere, and x/y/kind/name are never addressed, leaving a required-parameter gap.

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?

States a specific verb+resource combination ('Attach an explicit manufacturing NOTE') and scopes it to curved/periodic features that drawing_gate enumerates, which distinguishes it from the general add_annotation sibling by intent. It does not explicitly contrast itself against add_annotation or add_gdt_callout, so an agent must infer the boundary from the 'feature coverage' framing.

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?

It gives a real trigger condition: use this when drawing_gate enumerates a feature that a single number can't capture, and notes that the gate reads the note back as coverage. However, no sibling alternative is named and no 'when not to use' case is stated, leaving the choice between add_annotation and add_feature_note to inference.

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