Skip to main content
Glama
U-C4N
by U-C4N

Select Entities By Layer

analysis_select_by_layer
Read-only

Select all entities on a specified layer and return their handles. Compact mode provides a columnar summary with total entity counts and truncation flags.

Instructions

Get all entities on a specific layer. Returns entity list with handles.

Capped at MAX_LIST_LIMIT (default 5000). The plain list cannot say it was capped — the warning goes to the log stream, which most clients never show the model — so use compact=True when the count matters: its total is the layer's real population and truncated states whether the cap fired.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoProject to these fields, in this order (e.g. ['handle','type','layer']); 'properties.<key>' reaches one nested value. Omit for the full record; an unknown name errors and lists the valid ones.
compactNoReturn a columnar {fields, rows, count, offset, total, truncated, next_offset} envelope instead of dicts: much cheaper per row, and the only shape that reports truncation.
layer_nameYesLayer name to select entities from

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral traits: the MAX_LIST_LIMIT cap, the fact that the plain list cannot indicate truncation, the log-stream warning invisible to most clients, and the compact mode's 'total' and 'truncated' fields. This is rich, non-obvious context that significantly aids correct use.

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?

The description is concise and well-structured: one sentence stating the core function, then a focused paragraph about the cap and the compact workaround. Every sentence earns its place, with no fluff or repetition.

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?

The tool is a read-only selection operation with an output schema, so the description need not explain return values. It covers the essential caveat (truncation) and gives explicit guidance for the common pitfall. Combined with the schema and annotations, the description makes the tool's behavior fully understandable.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining the cap implications and why compact should be used when the count matters, supplementing the schema's already detailed compact parameter description. It does not add much for layer_name or fields, but the extra compact context justifies a slightly higher score.

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 opens with 'Get all entities on a specific layer,' a specific verb+resource that exactly matches the tool name. It also states the return type (entity list with handles) and differentiates from siblings like layer_list and analysis_select_by_type.

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?

Provides clear context for when to use the tool (to get layer entities) and gives a conditional usage guideline: 'use compact=True when the count matters.' However, it does not explicitly discuss alternatives or exclusions relative to sibling tools, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/U-C4N/Autocad-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server