Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

browse_models

Read-only

Browse Thingiverse 3D models by popularity, recency, or category to find printable designs for your next project.

Instructions

Browse Thingiverse models by popularity, recency, or category.

        Args:
            browse_type: One of "popular", "newest", or "featured".
            page: Page number (1-based, default 1).
            per_page: Results per page (default 10, max 100).
            category: Optional category slug (e.g. "3d-printing", "art");
                ``list_model_categories`` lists the slugs.  When given,
                ``browse_type`` is ignored and the category's models are
                listed instead.

        Returns model summaries similar to ``search_models``.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based, default 1). Default: 1.
categoryNoOptional category slug (e.g. "3d-printing", "art"); ``list_model_categories`` lists the slugs. When given, ``browse_type`` is ignored and the category's models are listed instead.
per_pageNoResults per page (default 10, max 100). Default: 10.
browse_typeNoOne of "popular", "newest", or "featured". Default: "popular".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.1
    • changedInput schema / properties / browse_type / description
      Previous value: -"Default: \"popular\"."New value: +"One of \"popular\", \"newest\", or \"featured\". Default: \"popular\"."
    • addedInput schema / properties / category / description
      Added value: +"Optional category slug (e.g. \"3d-printing\", \"art\"); ``list_model_categories`` lists the slugs.  When given, ``browse_type`` is ignored and the category's models are listed instead."
    • changedInput schema / properties / page / description
      Previous value: -"Default: 1."New value: +"Page number (1-based, default 1). Default: 1."
    • changedInput schema / properties / per_page / description
      Previous value: -"Default: 10."New value: +"Results per page (default 10, max 100). Default: 10."
  2. Changed7 schema fields changedv1.5.0
    • removedInput schema / properties / browse_type / default
      Removed value: -"popular"
    • addedInput schema / properties / browse_type / description
      Added value: +"Default: \"popular\"."
    • removedInput schema / properties / category / default
      Removed value: -null
    • removedInput schema / properties / page / default
      Removed value: -1
    • addedInput schema / properties / page / description
      Added value: +"Default: 1."
    • removedInput schema / properties / per_page / default
      Removed value: -10
    • addedInput schema / properties / per_page / description
      Added value: +"Default: 10."
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavior beyond that: pagination defaults/caps, the category-overrides-browse_type rule, and a note on the return shape ('model summaries similar to search_models'). It does not cover empty-result or invalid-category behavior, but for a read-only browse call this is solid.

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 opening sentence is well front-loaded and carries the core meaning. However, the following Args block duplicates the input schema field-for-field, which is pure redundancy and roughly doubles the length without adding information. Trimming to the first sentence plus the category-override and return-shape notes would be tighter.

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?

For a four-parameter, zero-required, read-only browse tool with full schema coverage and no output schema, the description covers what the tool does, how paging works, how the two browsing modes interact, and roughly what comes back. Only the absence of guidance on error/empty-category handling keeps it from full marks.

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 all four parameters with defaults and the enum-like values. The Args block in the description is essentially a verbatim restatement of those same field descriptions, adding no syntax, format, or edge-case detail the schema lacks. Baseline 3 applies.

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 and resource ('Browse Thingiverse models') plus the three browse axes, so an agent immediately knows this is a listing tool, not a search tool. It also signals the relationship to `search_models` and `list_model_categories`, though it never explicitly contrasts itself with `search_models`/`search_all_models`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational context: use `browse_type` for popular/newest/featured, use `category` for a category feed, and consult `list_model_categories` to discover slugs. The critical exclusion ('when category is given, browse_type is ignored') is spelled out. It stops short of saying when to prefer this over `search_models`, which is the one obvious gap.

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