Fab MCP

by ThreeNativeHQ

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List Smithsonian 3D files

smithsonian_list_files

Read-onlyIdempotent

List direct Smithsonian Open Access files with format, quality, compression, and orientation metadata.

Instructions

List direct Smithsonian Open Access files with format, quality, compression, and orientation metadata.

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": "smithsonian_list_files"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`modelId`	Yes
`quality`	No
`fileType`	No
`modelType`	No

Output Schema

Name	Required	Description	Default
`files`	Yes
`total`	Yes
`license`	Yes
`provider`	Yes
`nextCursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Sep 14, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description adds value by mentioning what metadata is returned (format, quality, compression, orientation). However, it does not describe pagination behavior or rate limits beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, but it omits critical information. Conciseness should not sacrifice clarity or completeness.

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 6 parameters (1 required), many enums, and an output schema, the description fails to explain pagination, filtering, or the relationship between modelId and files. Sibling context suggests this tool is part of a broader ecosystem, but no hints on how it fits.

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 hints at 'format' and 'quality' parameters but does not explain 'cursor', 'limit', 'fileType', 'modelType', or the required 'modelId'. 'Compression' and 'orientation' are not parameters but output fields, adding confusion.

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?

The description clearly states the action (list files) and resource (Smithsonian Open Access files). It mentions specific metadata types, distinguishing it from sibling tools like smithsonian_search_assets and smithsonian_get_asset. However, it does not explicitly differentiate from non-Smithsonian list tools.

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 on when to use this tool versus alternatives like asset_list_sources or polyhaven_list_files. The description does not mention prerequisites, filtering, or pagination.

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

Deploy Server