Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

asset_search

Read-only

Find candidate 3D assets online without downloading them, then review results by query, filters, or reference image before acquisition.

Instructions

Find candidate assets online without downloading 3D assets.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
filtersNo
image_data_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-source profile is covered. The description adds that nothing is downloaded, reinforcing the non-mutating nature, but says nothing about rate limits, result quality, or what a 'candidate' actually is.

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 front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification rather than tight scoping.

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?

For a four-parameter, zero-coverage, no-output-schema tool, the description leaves too much unstated: the meaning of the opaque 'filters' object, the image-search path, and any notion of result shape or ranking. An agent can guess the intent but not how to drive the parameters.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters, so the description carries the full burden and contributes nothing. It never mentions 'query', 'limit', 'filters', or 'image_data_url' — notably the image parameter, which implies an image-based search mode an agent would not otherwise anticipate.

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 resource ('Find candidate assets online') and adds a scoping qualifier ('without downloading 3D assets'). This implicitly separates it from acquisition siblings like asset_acquire, but it does not distinguish it from other search siblings such as catalog_search or huggingface_search_datasets.

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?

Usage is only implied: the 'without downloading' clause suggests a discover-then-acquire workflow, so an agent can infer this is the pre-acquisition step. There is no explicit when-to-use/when-not-to-use statement and no sibling alternative named.

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