Skip to main content
Glama

get_object

Read-onlyIdempotent

Retrieves a Sand3D object's full card by ID, including name, dataset, parts, joints, license, attribution, page URL, and its generating Python program. Use it to inspect or download a model's source code.

Instructions

Get the card of one Sand3D object: name, dataset, family, parts, joints, license, attribution string, page URL, and its generating Python program (sand3d library, millimeters, Z up). The program is cut to program_lines unless full_program=true.

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_id": "<object_id>"
    },
    "name": "get_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
object_idYesObject id from search_objects or find_similar.
full_programNoReturn the whole program.
program_linesNoHow many program lines to include.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the program payload is truncated by default and only returned whole when full_program=true, plus the domain conventions (sand3d library, millimeters, Z up) that shape how the returned program should be read.

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 sentences, zero filler. The payload enumeration is front-loaded and the truncation rule follows immediately, so the agent learns contents first and the size-control caveat second without scanning prose to find either.

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?

With no output schema, the description carries the burden of describing return values and it does so explicitly by listing the card's fields. Combined with the units/frame conventions and the truncation behavior, an agent has enough to call the tool and interpret its result without further documentation.

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 coverage is 100%, so a 3 is the baseline, but the description adds the precedence rule between the two program parameters — the program is cut to program_lines unless full_program=true — which the schema lists as independent defaults and never resolves. That interaction is real meaning beyond the structured fields.

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 (get) and resource (one Sand3D object card) and enumerates exactly what the card contains: name, dataset, family, parts, joints, license, attribution, page URL, and the generating Python program. This clearly separates it from search_objects (plural discovery) and download_object (file retrieval), even without naming them.

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?

There is no explicit when-to-use or when-not-to-use guidance in the description, and no named alternative. Usage is only implied: the object_id parameter description points back to search_objects or find_similar, which hints at the discovery-then-detail workflow, but the agent must infer it from the schema rather than the prose.

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