Sketchlib

Search 3D models

search_models

Search the Sketchlib library by keyword, optionally narrowed by category, tag, or face-count range. Returns paginated metadata and a preview image URL. has_more reports whether a further page exists; raise offset by limit to fetch it.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Filter by tag.
`limit`	No	Results per page, 1-50. Defaults to 20.
`offset`	No	Pagination offset.
`keyword`	Yes	Search terms, at least 3 characters. Matched against title, slug, tags, categories and description.
`category`	No	Filter by category.
`max_faces`	No	Maximum face count.
`min_faces`	No	Minimum face count.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 2026

removedInput schema / properties / author

Removed value: -{
-  "description": "Exact author name.",
-  "type": "string"
-}

changedInput schema / properties / keyword / description

Previous value: -"Search terms, at least 3 characters. Matched against title, slug, author, tags, categories and description."New value: +"Search terms, at least 3 characters. Matched against title, slug, tags, categories and description."

First observedOct 2, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses the return shape (paginated metadata plus a preview image URL) and the pagination contract (has_more indicates a further page; raise offset by limit to fetch it). It omits auth/rate-limit or result-cap behavior, which keeps it short of a 5.

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?

Three tight sentences: purpose and filters first, then return content, then the pagination recipe. No filler, and the most actionable detail (offset += limit) is saved for last where it belongs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain returns, and it does: paginated metadata, preview image URL, and the has_more/offset contract for paging. An agent can call this correctly and iterate pages without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every parameter including the 3-character keyword minimum and the 1-50 limit range. The description restates the filter dimensions (category, tag, face-count range) without adding syntax or matching-behavior detail beyond the schema, which is the baseline 3 case.

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 (Search) and resource (Sketchlib 3D model library) and enumerates the narrowing dimensions: category, tag, face-count range. The read-oriented search framing is clearly distinct from the get_model/download_model siblings by name, though the description never explicitly contrasts itself with them.

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?

Usage is implied by 'Search the Sketchlib library by keyword, optionally narrowed by...' which tells the agent this is the discovery entry point, but there is no explicit when-to-use vs get_model/download_model guidance and no stated prerequisites or exclusions.

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

All Sketchlib tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?