Skip to main content
Glama

Measure Angle

measure_angle
Read-only

Measures the angle in degrees between two planar faces or two straight edges, returning raw and supplementary values for design checks; read-only.

Instructions

Angle (degrees) between two planar faces or two straight edges.

a, b: object handles. a_ref, b_ref: REQUIRED sub-shape references, one per handle. Both must be the SAME kind:

  • face tags ('f_*' from list_faces/query_faces, or 'FaceN', or 1-based int) -> angle is between the faces' outward normals. Faces must be planar.

  • edge tags ('e_*' from list_edges, or 'EdgeN', or 1-based int) -> angle is between the edges' tangent directions. Edges must be straight. Mixing a face ref with an edge ref, a non-planar face, or a curved edge raises.

Units: degrees. Returns:

  • angle_deg: raw angle between the two direction vectors, 0..180.

  • supplement_deg: 180 - angle_deg (the complementary angle; use this for the acute reading when angle_deg is obtuse).

  • kind: "face" or "edge". Two adjacent box faces -> angle_deg 90. Two opposite parallel box faces -> angle_deg 180, supplement_deg 0. Read-only: measures, creates no geometry.

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": {
      "a": "<a>",
      "a_ref": "<a_ref>",
      "b": "<b>",
      "b_ref": "<b_ref>"
    },
    "name": "measure_angle"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes
a_refYes
b_refYes
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

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantial behavior beyond them: it names the error conditions that raise, specifies accepted reference formats, and because there is no output schema, it fully documents the returned fields angle_deg, supplement_deg, and kind. The read-only statement is redundant with the annotation but does not contradict it.

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 purpose is front-loaded and the bullet structure makes reference formats and return values easy to scan. It is somewhat long, and the closing 'Read-only: measures, creates no geometry' repeats the readOnlyHint annotation, but the examples and format details largely earn their space.

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?

With no output schema and low schema description coverage, the description carries the burden well: it covers input reference formats, error conditions, units, and return fields, and even gives concrete box-face examples to anchor angle versus supplement interpretation. An agent has enough information to call and interpret the tool correctly.

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

Parameters5/5

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

Schema description coverage is only 20%, so the description must compensate, and it does: it explains that a and b are object handles, that a_ref and b_ref are required sub-shape references, and lists the acceptable face and edge tag formats including f_*/e_*, FaceN/EdgeN, and 1-based integers. It also explains the semantic consequence of each reference kind (outward normals vs tangent directions).

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 states a specific measurement verb and resource: the angle in degrees between two planar faces or two straight edges. This is unmistakably distinct from sibling measurement tools such as measure_distance, bounding_box, or min_clearance, so an agent can select it without opening the schema.

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?

It provides clear validity conditions: both references must be the same kind, faces must be planar, and edges must be straight; mixing kinds or using curved/non-planar geometry raises. It does not explicitly contrast with alternatives like measure_distance or min_clearance, so it stops short of full when/when-not guidance.

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