Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_design_goals

Read-only

List saved design sessions and filter them by status, such as needing questions, ready to generate, or check results, to find the right goal for your next 3D printing task.

Instructions

List your saved design sessions (saved goals).

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_design_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum sessions to return (default 200, max 1000), applied after filtering. Default: 200.
filter_statusNo``"all"`` returns every session; ``"needs_questions"`` only sessions still in the Q&A phase; ``"ready_to_generate"`` committed sessions with nothing made yet; ``"checks_passed"`` / ``"checks_missed"`` / ``"not_fully_checked"`` made sessions by their LATEST making's measured result. ``"matches_what_you_asked_for"`` is the deprecated pre-reading spelling and filters like ``"checks_passed"``. Default: "all".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / filter_status / description
      Previous value: -"Default: \"all\"."New value: +"``\"all\"`` returns every session; ``\"needs_questions\"`` only sessions still in the Q&A phase; ``\"ready_to_generate\"`` committed sessions with nothing made yet; ``\"checks_passed\"`` / ``\"checks_missed\"`` / ``\"not_fully_checked\"`` made sessions by their LATEST making's measured result. ``\"matches_what_you_asked_for\"`` is the deprecated pre-reading spelling and filters like ``\"checks_passed\"``. Default: \"all\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 200."New value: +"Maximum sessions to return (default 200, max 1000), applied after filtering. Default: 200."
  2. Addedv1.5.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds nothing beyond that — no ordering, no iteration/pagination behavior, no note that results are post-filtered (which the schema hints at), and no explanation of what a 'session/goal' record is.

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?

A single short sentence with no filler, front-loaded on the verb and resource. It is efficient but borders on under-specification given the crowded namespace of listing tools.

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 two-optional-param, read-only list tool with full schema documentation and no output schema, the definition supplies enough to invoke correctly. The only shortfall is the undefined framing of 'design sessions (saved goals)' relative to sibling listers.

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 both limit (default 200, max 1000, applied after filtering) and the filter_status enum-like spellings are fully documented in the schema. The description adds no meaning beyond it, so 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?

States a specific verb and resource ('List your saved design sessions') and glosses it with '(saved goals)'. However, it never distinguishes this from closely named siblings like list_designs, list_cached_designs, or list_snapshots, so an agent cannot tell which lister returns what without reading schemas.

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 and no exclusions. Given the very large sibling set of design-listing tools (list_designs, list_design_branches, list_cached_designs, list_public_designs), the absence of any routing hint is a real 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