Skip to main content
Glama
Sign In
qidi-mcp

qidi-mcp

by couplet-physical-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_box_filament_options

Read-onlyIdempotent

Search the printer's built-in filament profiles, color swatches, and vendors to find exact names for setting box slot filaments; filter by query or list all options.

Instructions

Search the filament profiles, colour swatches and vendors the printer itself knows (its officiall_filas_list.cfg). Use it to find the exact name to give set_box_slot_filaments. query filters profiles by words in their name or type ('petg', 'matte', 'cf'); leave it empty for all of them. Colours are the printer's fixed swatches, each with a plain-English name.

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

Input Schema

NameRequiredDescriptionDefault
queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real context beyond that: the data comes from the printer's fixed config file and colours are fixed swatches with plain-English names, which tells the agent results are static and not user-editable.

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?

Front-loaded with the purpose, then the downstream consumer, then the parameter behavior — a sensible order with little waste. Minor blemishes: the typo 'officiall_filas_list.cfg' and a slightly dense final sentence.

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?

An output schema exists, so return values need no explanation, and the single optional parameter is fully described. For a simple read-only lookup this is nearly complete; only the relationship to get_filament_presets is left implicit.

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?

Schema coverage is 0%, so the description must carry the parameter, and it does: query filters by words in profile name or type, with concrete examples ('petg', 'matte', 'cf'), and empty returns everything. It stops short of stating matching semantics (substring vs token, case sensitivity).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the filament profiles, colour swatches and vendors') and pins the data source to the printer's own officiall_filas_list.cfg, which separates it from the sibling get_filament_presets. An agent can tell what it returns without opening the schema.

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?

Explicitly routes the agent: 'Use it to find the exact name to give set_box_slot_filaments', naming the downstream sibling. It does not state when to prefer get_filament_presets instead, so the alternative-selection guidance is incomplete but the primary use case is clear.

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