Fab MCP

by ThreeNativeHQ

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Search Sketchfab models

sketchfab_search_models

Read-onlyIdempotent

Search public Sketchfab models and return per-model license, author, geometry, and archive metadata.

Instructions

Search public Sketchfab models and return per-model license, author, geometry, and archive metadata.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sketchfab_search_models"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`query`	No
`cursor`	No
`sortBy`	No	relevance
`animated`	No
`category`	No
`licenses`	No
`staffPicked`	No
`downloadable`	No

Output Schema

Name	Required	Description	Default
`items`	Yes
`provider`	Yes
`nextCursor`	No
`downloadAuthentication`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Sep 14, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds value by detailing returned metadata fields, which goes beyond what annotations convey. 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?

Single sentence with 15 words, front-loaded with purpose and return info. No wasted words, to the point.

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?

Basic purpose and return are covered, but parameter usage is not explained. Output schema may clarify return structure, but for a tool with 9 optional parameters, more guidance is needed for effective use.

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% with 9 parameters. Description does not explain any parameter semantics (e.g., query, sortBy, filters). It must compensate but fails, leaving agents to guess parameter roles.

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?

Description clearly states 'Search public Sketchfab models' with verb+resource, and specifies return fields (license, author, geometry, archive metadata). This distinguishes from siblings like sketchfab_get_model (single model) or sketchfab_list_categories (categories).

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 explicit when-to-use or when-not-to-use guidance. Implied by context but no alternatives named. Sibling list provides context but description lacks usage instructions.

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

Deploy Server