Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

huggingface_acquire_asset

Download a selected dataset USD asset and its resolvable dependencies at a pinned commit, then poll job status to confirm acquisition.

Instructions

Download one selected dataset USD and resolvable dependencies at a pinned commit; poll job_status.

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": {
      "repo_id": "<repo_id>",
      "revision": "<revision>",
      "path": "<path>"
    },
    "name": "huggingface_acquire_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
repo_idYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose two important traits: the operation is asynchronous (poll job_status) and it transitively fetches dependencies at a pinned commit. It says nothing about authentication for gated repos, where artifacts land on disk, size/time expectations, or whether an existing checkout is overwritten, which are material for a download job.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the action and object front-loaded and the follow-up step attached via a semicolon; no filler. Only the unexplained 'USD' abbreviation costs a point on clarity-per-word.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex asynchronous multi-file acquisition tool with zero annotation coverage, no output schema, and no parameter documentation in the schema, so the description should have covered destination behavior, auth, and failure semantics. It delivers the job-model hint and dependency behavior but leaves too much unspecified for an agent to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three required parameters. The description only weakly maps to them: 'pinned commit' hints that revision should be a commit SHA, and 'one selected dataset' hints at repo_id, but 'path' is never explained at all (file within the repo? destination directory?), leaving an agent to guess the most error-prone argument.

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?

The description names a specific verb (Download) and a specific resource (one selected dataset USD plus resolvable dependencies at a pinned commit), which separates it from siblings like huggingface_list_assets, huggingface_search_datasets and asset_acquire. It falls short of 5 only because 'USD' is domain jargon and 'selected' leaves the selection source implicit.

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 phrasing 'one selected dataset' implies this runs after a search/inspect step, and 'poll job_status' explicitly names the follow-up tool, which is real routing guidance. However, there is no statement of when NOT to use it, no mention of a prerequisite selection step by name, and no alternative download path is contrasted.

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