Skip to main content
Glama

select_by_axis

Selects vertices, edges, or faces on one side of a mesh along an X, Y, or Z axis to isolate top, front, or half geometry for modeling.

Instructions

Select the vertices, edges and faces on one side of a mesh along an axis.

The usual way to say "the top", "the front" or "the left half" of one object. To select whole objects in the scene, use select_objects.

Args: object_name: Name of the mesh object. axis: One of: X, Y, Z. sign: POS for the positive half, NEG for the negative half, split at the middle of the object's bounding box (the middle counts for both); ALIGN for geometry lying on that middle plane. extend: Add to the current selection instead of replacing it.

Returns: Dict with how many elements were selected.

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": {
      "object_name": "<object_name>"
    },
    "name": "select_by_axis"
  }
}

Input Schema

NameRequiredDescriptionDefault
axisNoZ
signNoPOS
extendNo
object_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it explains that selection replaces the current selection unless extend is true, and defines POS/NEG/ALIGN split behavior around the object's bounding-box midpoint. It does not mention whether the mesh must be in edit mode or what current mode/active-object prerequisites apply, which is a meaningful omission for a mesh-selection tool.

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-loads the core operation, then gives the sibling-tool distinction, then structured Args and Returns notes. Every sentence contributes useful selection or parameter context without waste.

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?

Covers the selection scope, all four parameters, the replace/extend behavior, and return count. For a mesh-selection tool, however, a note about required mesh/edit mode or active-object context would make it fully complete.

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 0%, so the description must compensate, and it does: object_name, axis values X/Y/Z, sign values POS/NEG/ALIGN with midpoint semantics, and extend's add-versus-replace behavior are all documented. This adds substantial meaning beyond the bare enum/default schema.

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 and resource: selecting vertices, edges, and faces of a mesh on one side of an axis. It also explicitly distinguishes itself from sibling select_objects by saying that tool is for selecting whole objects in the scene.

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?

Explains the common use case as saying "the top", "the front" or "the left half" of one object, and names select_objects as the alternative for whole-object selection. The condition for choosing between the two is explicit.

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