Skip to main content
Glama
playcanvas

PlayCanvas Editor MCP Server

Official
by playcanvas

store_search

Locate assets in the PlayCanvas Editor store by specifying search terms, sorting order, and pagination parameters for efficient project integration.

Instructions

Search for an asset in the store

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
orderNo
searchYes
skipNo

Implementation Reference

  • The execution handler for the 'store_search' MCP tool. It transforms the optional 'order' parameter using the orderEnum helper and forwards the search parameters (search, order, skip, limit) to the WebSocket service's 'store:playcanvas:list' method.
    ({ search, order, skip, limit }) => {
        return wss.call('store:playcanvas:list', {
            search,
            order: order ? orderEnum[order] : undefined,
            skip,
            limit
        });
    }
  • Zod input schema defining the parameters for the 'store_search' tool: required 'search' string, optional 'order' ('asc' or 'desc'), optional 'skip' and 'limit' numbers.
    search: z.string(),
    order: z.enum(['asc', 'desc']).optional(),
    skip: z.number().optional(),
    limit: z.number().optional()
  • MCP tool registration for 'store_search' using mcp.tool(), specifying the tool name, description, input schema, and inline handler function.
    mcp.tool(
        'store_search',
        'Search for an asset in the store',
        {
            // store: z.enum(['playcanvas', 'sketchfab']).optional(),
            search: z.string(),
            order: z.enum(['asc', 'desc']).optional(),
            skip: z.number().optional(),
            limit: z.number().optional()
        },
        ({ search, order, skip, limit }) => {
            return wss.call('store:playcanvas:list', {
                search,
                order: order ? orderEnum[order] : undefined,
                skip,
                limit
            });
        }
    );
  • Helper object mapping sort order strings ('asc', 'desc') to numeric values (1, -1) for use in the handler's order parameter transformation.
    const orderEnum = {
        'asc': 1,
        'desc': -1
    };
  • src/server.ts:83-83 (registration)
    Top-level invocation of the store register function in the main server setup, which registers the 'store_search' tool among others.
    registerStore(mcp, wss);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'Search' but doesn't disclose behavioral traits like whether this is read-only, requires authentication, has rate limits, or what the return format looks like. The description is minimal and lacks critical operational details.

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?

The description is a single, efficient sentence with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly, though this conciseness comes at the cost of detail.

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?

Given the complexity (4 parameters, 0% schema coverage, no annotations, no output schema), the description is incomplete. It doesn't explain return values, error conditions, or how parameters interact, leaving significant gaps for a search tool with multiple inputs.

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%, so the description must compensate. It doesn't add any meaning beyond the schema—no explanation of what 'search' parameter does, how 'limit' or 'skip' affect results, or the purpose of 'order'. With 4 parameters and no semantic context, this is inadequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Search for an asset in the store' clearly states the verb ('Search') and resource ('asset in the store'), but it's vague about what constitutes an 'asset' and doesn't differentiate from siblings like 'list_assets' or 'store_download'. It provides basic purpose but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'list_assets' or 'store_download'. The description implies a search function but doesn't specify context, prerequisites, or exclusions, leaving the agent to infer usage.

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

Related 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/playcanvas/editor-mcp-server'

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