Skip to main content
Glama
Sign In
3D Texel MCP server

3D Texel MCP server

by Gatyh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Asset details

get_asset
Read-only

Fetch full details for one 3D asset, including description, tags, license, price, API download eligibility, and ownership status.

Instructions

Full details of one asset: description, tags, license, price, whether it can be downloaded through the API and whether the user already owns it.

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": {
      "asset_id": "<asset_id>"
    },
    "name": "get_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that, the description discloses the shape of the response (permissions/downloadability and ownership flags), which is meaningful behavioral context for a read tool with no output schema.

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?

One front-loaded sentence with no filler; the field enumeration is dense but all of it is informative. Minor weakness: it reads as a noun fragment rather than stating the action verb explicitly.

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?

For a one-parameter read tool with an existing title and readOnly annotation, the main gaps are the provenance/format of asset_id and any indication of what happens for nonexistent or non-owned assets. The field list compensates for the absent output schema, but parameter guidance is missing.

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% and the single parameter (asset_id, type integer) carries no description. The tool description says nothing about what asset_id is or where to obtain it (e.g., from search_assets), leaving the parameter entirely undocumented.

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+resource ('Full details of one asset') and enumerates the concrete fields returned (description, tags, license, price, downloadability, ownership), which clearly separates it from search_assets. It doesn't explicitly reference a sibling or say it addresses a single asset_id vs. a listing, but the singular scope is evident.

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, no exclusion clause, and no mention of the obvious alternative (search_assets to discover assets before fetching details). The agent must infer that this tool is for lookup by a known asset_id.

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