Skip to main content
Glama

list_models

List available parametric OpenSCAD models with parameter schemas, presets, resolved defaults, and licenses to choose and configure models before STL generation.

Instructions

List available parametric models with parameter schemas, presets, resolved defaults and licenses.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden. 'List available' clearly signals a non-mutating read, and the enumeration of returned fields (schemas, presets, resolved defaults, licenses) tells the agent what each entry represents. It stops short of stating auth requirements, pagination, or whether the catalog is static.

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?

A single dense sentence, front-loaded with the action and resource, followed by the list of returned fields. No filler, no redundancy, nothing that could be cut without losing information.

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 zero-parameter read tool with an output schema, the description covers everything an agent needs to decide to call it and what it will get back. The one gap is the missing link to 'generate' — the natural reason an agent would look up models in the first place.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate — the baseline applies. The description instead spends its words on what the (empty) call returns, which is the useful place to spend them.

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?

Uses a specific verb plus resource ('List available parametric models') and enumerates what each entry contains: parameter schemas, presets, resolved defaults, and licenses. That is far more informative than a bare name restatement, though it never explicitly contrasts itself with the 'generate' sibling.

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 only implied — an agent can infer this is a discovery tool to call before 'generate' to find valid models, but the description never says when to use it, when not to, or that it is the predecessor to generation. With a parameterless read tool the omission is tolerable but real.

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