Fab MCP

by ThreeNativeHQ

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Get a Sketchfab model

sketchfab_get_model

Read-onlyIdempotent

Get public metadata and explicit Creative Commons requirements for one Sketchfab model.

Instructions

Get public metadata and explicit Creative Commons requirements for one Sketchfab model.

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": {
      "modelId": "<modelId>"
    },
    "name": "sketchfab_get_model"
  }
}

Input Schema

Name	Required	Description	Default
`modelId`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`tags`	Yes
`author`	No
`license`	No
`animated`	Yes
`archives`	Yes
`embedUrl`	No
`provider`	Yes
`faceCount`	No
`likeCount`	No
`updatedAt`	No
`viewCount`	No
`viewerUrl`	Yes
`categories`	Yes
`description`	No
`publishedAt`	No
`vertexCount`	No
`downloadable`	Yes
`thumbnailUrl`	No
`ageRestricted`	No
`downloadCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Sep 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by specifying what is returned (public metadata and Creative Commons requirements), beyond what annotations provide. No contradictions.

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 sentence that instantly conveys the action and target, with no filler or redundant information. Every word earns its place.

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?

The tool has an output schema (covering return values), simple parameters, and the description states the retrieval scope. It is complete enough for this straightforward read operation.

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 coverage is 0%, so the description must compensate. It does not explain the modelId parameter beyond the schema's pattern, missing an opportunity to clarify its meaning or format.

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 uses a specific verb ('Get') and resource ('public metadata and explicit Creative Commons requirements for one Sketchfab model'), clearly distinguishing from sibling tools like sketchfab_search_models and sketchfab_get_downloads.

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 retrieving a single model's metadata and license info, but it lacks explicit when-to-use guidance or comparisons with siblings. No exclusions or alternatives are mentioned.

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

Deploy Server