Skip to main content
Glama

List Edges

list_edges
Read-only

Retrieve all edges of a shaped object with stable tags and geometric descriptors for accurate downstream modeling and analysis.

Instructions

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

Returns [{tag, index, kind, length, centroid, axis?, radius?}, ...]. Same stability story as list_faces.

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_edges"
  }
}

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

B3.4/5.0
Behavior4/5

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

Annotations already cover the read-only, closed-world safety profile, and the description adds real value beyond them: it documents the returned record shape ({tag, index, kind, length, centroid, axis?, radius?}) and asserts tag stability, which matters for downstream edge-referencing calls. It stops short of defining what 'stable' means concretely (e.g. across rebuilds or topology changes), deferring to list_faces.

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?

Two short lines, purpose first, return contract second — no filler. The only weakness is that 'Same stability story as list_faces' is a cross-reference that forces the agent to look up another tool to understand the guarantee.

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?

For a read-only list tool with no output schema, the return record and stability claim cover most of what's needed, but the undefined 'stable' semantics and the undocumented handle parameter leave gaps an agent would hit when chaining into edge-modifying 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 50%: workspace is documented in the schema, handle is bare. The description's phrase 'of a shaped object' gives handle implicit meaning as a shape handle, but adds no format or resolution detail beyond that, so it sits at the baseline for partial coverage.

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 and resource ('List all edges of a shaped object') plus what makes the output special (stable tags + descriptors). It references the sibling list_faces for the stability contract, which hints at the pairing, but does not explicitly say how it differs from query_faces or resolve_edge.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance. An agent must infer that this is the discovery step before fillet_edges or chamfer_edges, and nothing tells it whether to prefer list_edges over query_faces or resolve_edge for a given task.

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