Skip to main content
Glama

list_datasets

Read-onlyIdempotent

List Sand3D datasets with object counts and family names, optionally filtering to one dataset to see all its families for object searches.

Instructions

List Sand3D datasets (objaverse household items, cad mechanical parts, articraft articulated objects, simready warehouse assets, automate mechanical assemblies) with object counts and their families. Pass dataset to see all families of one dataset; family keys or labels can be used in search_objects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
datasetNoShow all families of this dataset only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing what the call returns (object counts and family groupings), which matters because there is no output schema. It says nothing about result size or ordering, hence not a 5.

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, both front-loaded: purpose and return content first, then the filtering mode and the downstream handoff. The parenthetical list of dataset families is dense but each entry is informative rather than filler, and there is no redundant restatement of the title or name.

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 single optional-parameter, non-destructive listing tool with no output schema, the description covers what it returns and how to consume the output. Nothing an agent needs to call it correctly is missing; only details like ordering or result size are absent, and those are minor here.

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 the baseline is 3. The description earns extra credit by framing the parameter as a filter ("Pass dataset to see all families of one dataset") and by explaining what the resulting family keys and labels are for — reuse in search_objects — which is meaning the schema does not convey.

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?

Specific verb plus resource ("List Sand3D datasets") with the concrete dataset families enumerated in parentheses and the return contents ("object counts and their families") stated up front. It also distinguishes itself from search_objects by positioning the output as input material for that sibling, so an agent can tell the browse tool from the search tool.

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?

Explicitly states the two usage modes: call with no argument to enumerate all datasets, or pass 'dataset' to see all families of one. It also tells the agent how to use the results ("family keys or labels can be used in search_objects"), which is a clear handoff to the alternative. It stops short of an explicit when-not-to-use rule, but the browse-vs-search split is unambiguous.

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