Skip to main content
Glama

List Faces

list_faces
Read-only

Lists all faces of a shaped object with stable tags and geometric descriptors, so you can reference faces by tag in later calls instead of fragile FaceN indexes.

Instructions

List all faces of a shaped object with stable tags + geometric descriptors.

Returns [{tag, index, kind, area, centroid, normal?, axis?, radius?}, ...]. Tags survive geometry edits as long as the face's surface kind, area, centroid, and (where meaningful) normal/axis/radius do not change. Use the tag in subsequent calls instead of the FaceN index.

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": {
      "handle": "<handle>"
    },
    "name": "list_faces"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes
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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description then earns credit by disclosing non-obvious behavior: the exact return tuple shape and, more importantly, the invariance contract for tags (they survive edits only while kind/area/centroid/normal/axis/radius hold). That stability caveat materially affects how an agent should cache tags.

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?

Front-loaded with purpose, then return shape, then the stability rule, then the practical takeaway. The inline field list is dense but earns its space since there is no output schema. Minor slack only.

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

Completeness4/5

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

With no output schema, the description correctly supplies the return contract and the tag-stability semantics, which is the bulk of what an agent needs. Missing only minor items like handle provenance and failure behavior on an invalid handle.

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?

Coverage is 50%: workspace is documented in the schema, handle is not. The description implies handle identifies a "shaped object" and that the output is face-tagged, but adds no format or source guidance for the handle, so it only partially compensates for the schema gap. Baseline 3.

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 first sentence names a specific verb and resource ("List all faces of a shaped object") and adds the distinguishing value proposition of stable tags plus geometric descriptors. It does not, however, explicitly separate itself from near-name siblings like query_faces, resolve_face, or list_edges, so an agent must infer the boundary.

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?

"Use the tag in subsequent calls instead of the FaceN index" gives a downstream workflow hint, which is real but narrow. There is no statement of when to prefer this over query_faces or resolve_face, and no preconditions such as what state the object must be in.

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