Skip to main content
Glama
BricsCAD MCP

BricsCAD MCP

by alesdev88

bricscad_get_entity

Read-only

Retrieve a drawing entity by handle and return its type, layer, and all DXF group codes as [code, value] pairs for inspection and auditing.

Instructions

Return one entity's type, layer and all its DXF group codes, as [code, value] pairs.

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": "bricscad_get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value by disclosing the payload shape (type, layer, DXF code pairs), but says nothing about failure behavior for an invalid handle or whether the entity must be in the active drawing.

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?

A single front-loaded sentence with no filler; the output format is stated inline where it is most useful.

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?

With an output schema present, the return-value explanation is a bonus rather than a requirement, and the one-parameter surface is inherently simple. What is missing is the operational context an agent needs before calling: handle validity expectations and any prerequisite that a drawing be open/focused.

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?

Only one parameter (handle) at 0% schema description coverage, and the description never explains that it is the DXF entity handle or what format it takes. The 'one entity' phrasing does at least confirm the parameter selects a single entity, giving partial compensation for the coverage gap.

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 ('Return') and resource ('one entity's type, layer and all its DXF group codes') plus the exact output encoding as [code, value] pairs. This clearly separates it from bulk siblings like bricscad_query_entities or bricscad_list_layers by its single-entity scope, though it never names those alternatives explicitly.

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 phrase 'one entity' implies use for single-entity inspection rather than batch queries, which is a reasonable implicit routing signal. However, there is no explicit when-to-use, no stated prerequisite (e.g., an open drawing, a valid handle), and no named alternative for listing many entities.

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