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

Find Entities in Region

analysis_find_in_region
Read-only

Find all entities inside a rectangular area by specifying the region bounds (min/max X, Y). Optionally project fields or use compact output to control result size.

Instructions

Find all entities within a rectangular region (crossing selection).

Uncapped: a window over a busy drawing returns every hit. Project with fields and/or compact before widening the window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
x1YesRegion minimum X
x2YesRegion maximum X
y1YesRegion minimum Y
y2YesRegion maximum Y
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.

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 the important uncapped behavior: 'a window over a busy drawing returns every hit.' It also suggests performance-oriented usage with fields/compact. This adds behavioral context without contradicting annotations.

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 only two sentences: a clear one-sentence definition followed by an actionable warning. It is front-loaded with the core purpose and contains no filler.

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?

Given the rich input schema, readOnlyHint annotation, and existence of an output schema, the description covers the critical non-obvious behavior (uncapped results) and mitigation. No major contextual gap remains for an agent to invoke the tool safely.

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?

The input schema already provides 100% description coverage for all six parameters, including details for x1/x2/y1/y2, fields projection, and compact envelope. The description's mention of fields/compact reinforces their use but adds no new parameter meaning beyond what schema states.

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 begins with 'Find all entities within a rectangular region', giving a specific verb and resource scope. The parenthetical '(crossing selection)' clarifies the selection semantics and distinguishes this analysis query from sibling selection tools like selection_window.

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?

The description provides operational advice ('Project with fields and/or compact before widening the window') and warns about the uncapped result set, which implies when to use lightweight projections. However, it does not explicitly compare against sibling tools such as selection_window or entity_list, leaving the choice to the agent based on naming.

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