Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_published_models

Read-only

Lists models published to marketplaces, with optional filtering by marketplace name and a limit on results. Use it to find which designs are available and where they are listed.

Instructions

List models that have been published to marketplaces.

        Args:
            marketplace: Filter by marketplace name (optional).
            limit: Maximum number of results (default 50).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (default 50). Default: 50.
marketplaceNoFilter by marketplace name (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 50."New value: +"Maximum number of results (default 50). Default: 50."
    • addedInput schema / properties / marketplace / description
      Added value: +"Filter by marketplace name (optional)."
  2. Changed3 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -50
    • addedInput schema / properties / limit / description
      Added value: +"Default: 50."
    • removedInput schema / properties / marketplace / default
      Removed value: -null
  3. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description adds essentially nothing beyond that. It does not mention pagination/offset behavior, ordering, or what a returned model entry looks like, so the extra behavioral context is minimal.

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 purpose is correctly front-loaded in one clear sentence, but the following Args block is pure duplication of the input schema and earns no place. A single sentence would have been sufficient.

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?

This is a simple two-parameter, zero-required read tool with full annotation coverage, so much of the burden is already met. However, with no output schema, the description says nothing about the shape of the returned list (fields per model, ordering), which would help an agent consume the result.

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% and the Args block repeats the schema text verbatim, adding no new meaning for marketplace or limit. With the schema doing the heavy lifting, the baseline of 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?

The first sentence gives a specific verb and resource ("List models that have been published to marketplaces"), which is far clearer than a bare name restatement. It does not distinguish itself from nearby siblings such as browse_models, search_models, or list_cached_models, so an agent has no textual signal for choosing among them.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. The agent must infer from the name alone that this is a discovery/listing call rather than a search or browse call, and the description never clarifies that distinction.

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