Skip to main content
Glama

search_assets

Search external 3D asset providers such as Poly Haven, Sketchfab, and Poly Pizza by source and query to find models, materials, or assets for Blender scenes.

Instructions

Search external asset providers (polyhaven, sketchfab, polypizza).

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": {
      "source": "<source>",
      "query": "<query>"
    },
    "name": "search_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
sourceYes
asset_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden and discloses almost nothing beyond "this searches external providers." It does not mention network dependency, whether API keys or credentials are needed, rate limits, pagination, or failure behavior when a provider is unreachable — all material for a tool that reaches third-party services.

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 zero wasted words, which is structurally sound. Its compactness comes at the cost of the missing detail noted elsewhere, but as a conciseness measure it is efficient.

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?

The output schema removes the need to explain return values, but for a four-parameter, network-backed search with no annotations, the definition is thin. Required-parameter meaning, provider selection, and any auth or rate-limit expectations are all absent, leaving the agent under-equipped relative to the tool's complexity.

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% across four parameters, so the description must compensate and largely does not: it never maps the provider names to the required `source` parameter, and says nothing about `query` syntax, `limit` behavior, or what values `asset_type` accepts. The parenthetical provider list is the only real value-add, implicitly hinting at valid `source` values.

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?

"Search external asset providers" gives a specific verb plus resource and names three concrete providers, so the agent knows exactly what domain this touches. It stops short of differentiating from any alternative search/download path, so it lands at a clear-but-undifferentiated 4.

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?

There is no when-to-use guidance: nothing says whether this is for finding downloadable models before importing them, how it relates to any import/material tools, or under what conditions an agent should call it at all. Provider choice between polyhaven, sketchfab and polypizza is listed but never explained as a decision the caller must make.

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

Deploy Server

Other Tools