Skip to main content
Glama
sansaks-jpg

Gamedev All-in-One MCP

by sansaks-jpg

Roblox Search Decal

roblox_search_decal

Search the Roblox Creator Store for 2D images, decals, and textures. Returns direct PNG URLs for immediate use in your game.

Instructions

Search for 2D images, decals, textures, and sprites (e.g. wood texture, logo, UI icon, sword decal) in the Roblox Creator Store. Returns direct PNG image URLs for rendering in chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesKeyword to search for (e.g. 'iron texture', 'blood splatter', 'cat face').
limitNoMaximum number of search results (default 10).
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states it returns direct PNG URLs and performs a search (read-only). However, it does not disclose potential API limits, pagination behavior, or whether results are sorted by relevance.

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 succinct sentences: first defines scope with examples, second specifies output format. No filler, front-loaded with key information.

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 simple search tool with two parameters and no output schema, the description adequately covers what it searches, where, and what it returns. It lacks details on result ordering or asset metadata, but is sufficient for an agent to use correctly.

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

Parameters3/5

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

Schema coverage is 100% with descriptions for both keyword and limit. The description adds example values for keyword but does not meaningfully extend beyond the schema, achieving the baseline score.

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 2D images, decals, textures, and sprites in the Roblox Creator Store, with concrete examples. This distinguishes it from sibling tools like roblox_search_asset3d (for 3D models) and roblox_search_toolbox (for broader toolbox items).

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 2D image searches but does not explicitly state when to use this tool vs alternatives. It lacks references to sibling tools or conditions under which another search tool would be preferable.

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