Skip to main content
Glama
sansaks-jpg

Gamedev All-in-One MCP

by sansaks-jpg

Roblox Search 3D Asset

roblox_search_asset3d

Search the Roblox Creator Store for 3D assets like trees, rocks, buildings, or cars using keyword queries with an optional result limit.

Instructions

Search specifically for 3D Models, props, meshes, and visual assets (e.g. tree, rock, building, car) in the Roblox Creator Store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesKeyword to search for (e.g. 'oak tree', 'mossy rock', 'sport car').
limitNoMaximum number of search results (default 10).
Behavior2/5

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

No annotations are provided, and the description only says 'search specifically'. It does not disclose behavioral traits such as how results are returned, pagination, side effects, or safety profile.

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?

A single sentence that front-loads the purpose with no wasted words. Highly concise and clear.

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

Completeness3/5

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

Given low complexity (2 params, no output schema), the description is adequate but lacks details on return format or result handling, which could be helpful.

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% but description adds value with concrete examples for keyword and mentions default for limit, providing helpful context beyond the schema.

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?

The description clearly states it searches for 3D Models, props, meshes, and visual assets, distinguishing it from sibling tools like roblox_search_decal or roblox_search_toolbox.

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 description implies usage for 3D asset search but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sansaks-jpg/gamedev-all-in-one-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server