Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_public_design

Read-only

Read a public Kiln design page by username and slug to retrieve its details from kiln3d.com/@username/slug.

Instructions

Read the public design page at kiln3d.com/@username/slug.

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": {
      "username": "<username>",
      "slug": "<slug>"
    },
    "name": "get_public_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe design's address on the owner's page: the part after ``@username/``.
usernameYesThe owner's username: the part of the address after ``@``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

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 only the address shape, not what happens on a private, missing, or renamed design, nor whether it returns rendered HTML or structured design data — meaningful gaps for a fetch tool with no output schema.

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

Conciseness4/5

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

One short sentence with the resource and address pattern front-loaded and no filler. It is efficient, though the terseness is what leaves the usage and return-behavior gaps unaddressed.

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?

For a simple two-parameter read tool the definition is still thin: with no output schema, the description never says what the page read yields (markup, design metadata, components) or how failures are surfaced. An agent could invoke it but cannot predict 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 coverage is 100% and the schema already explains slug ('the part after @username/') and username ('the part after @'). The description's '@username/slug' notation restates that mapping rather than adding new semantics such as case sensitivity or URL-encoding behavior, so the 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?

The description gives a specific verb ('Read') and resource ('the public design page') and pins the location with the URL form 'kiln3d.com/@username/slug', which makes the public scope explicit. It does not name the near-siblings (get_design, search_public_designs, fork_public_design), so differentiation relies on the word 'public' alone.

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 at all: nothing tells the agent to prefer this over get_design for own designs, search_public_designs for discovery, or fork_public_design when a copy is wanted. The public URL pattern implicitly signals the context, but no exclusions or alternatives are stated.

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