Skip to main content
Glama

Get Object

get_object
Read-only

Retrieve a handle's properties and shape statistics to inspect FreeCAD objects when no dedicated tool exposes the needed data.

Instructions

Dump a handle's properties + shape stats. Useful when no dedicated tool exposes what you need.

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

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the call returns raw properties plus shape statistics (a 'dump'), which is useful since there is no output schema. It does not disclose response size/verbosity, failure behavior for invalid handles, or whether output is machine-parsable.

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?

Two short sentences, zero filler, with what the tool returns front-loaded ahead of the fallback guidance. Nothing to trim.

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?

For a low-risk, read-only introspection tool with no output schema, the description covers the essential question (what do I get back — properties and shape stats) and when to reach for it. The remaining gap is handle provenance and the exact contents of 'shape stats', which is a moderate but not critical omission.

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 the workspace parameter is documented in the schema (50% coverage); the required 'handle' parameter has no description. The description implies handle identifies the object being dumped, but never says what a handle looks like or where to obtain one (register_handle, list_objects), so the key required parameter remains underspecified.

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 object: dump the properties and shape statistics for a given handle. It also implicitly positions itself as an introspection/fallback tool. It falls short of 5 because 'handle' and 'shape stats' are server-specific jargon left undefined, and there is no explicit contrast with the many specialized siblings (query_faces, bounding_box, mass_properties, list_objects).

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?

'Useful when no dedicated tool exposes what you need' gives a fallback condition, which is real guidance. But it names no concrete alternative and gives no exclusion rules or prerequisites — an agent must scan the enormous sibling list itself to decide whether a dedicated tool exists.

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