Skip to main content
Glama
chartergroup

topopt

by chartergroup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Find a 3D printer

find_printer
Read-onlyIdempotent

Looks up a 3D printer by user-provided name in the shipped catalog and work-folder printer list, returning its profile and print parameters to configure a run without asking for bed size or process.

Instructions

Find a 3D printer by name in the catalog that ships with topopt and in the user printers of the work folder (topopt-printers.yaml). It reads; it changes nothing.

The user only names the printer; the tool knows the print parameters. Use it when the user says which printer they have ("Bambu P1S", "my Prusa MK4S"), before you ask for a bed size or a process. name: the model as the user says it. Case, punctuation, the maker name and the words "my" and "printer" do not matter ("p1s", "Bambu Lab P1S" and "bambu p1 s" are one printer). Returns: ok, status, query, catalog_version, matched_by, origin, profile, derives, candidates, differs, suggestions, vendors, user_file, note.

  • "match": profile is the printer: id, name, origin (catalog or user), bed_mm, build_height_mm, nozzle, temperatures, enclosure, nozzle material, extruder, and the source of the values (source_url, opened, tag, field_sources, note). A value that the source does not give is null (unknown): say so. derives says what print.printer_model: <id> sets in a run (the bed and the printer type, when the YAML does not give them) and what the profile cannot give.

  • "ambiguous": candidates and differs (the facts on which they differ). Ask the user which one; do not pick for them. matched_by is "partial" when the text is only a part of a name (one candidate too: a similar model can have other numbers).

  • "none": suggestions ("did you mean": never taken by itself) and a note on how to go on: look up the maker page and save_printer the values, or ask the user. user_file: path, exists, entries, problems. A problem in the file is a fact; the shipped catalog still works. Next: show the user the derived values, then save_preferences(print={"printer_model": id}) keeps the printer, or write print: {printer_model: <id>} in the YAML. A bed_mm or printer_type in the YAML wins. With a printer, the print report also compares the part height with its build height.

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly and idempotent annotations, it discloses matching behavior, how ambiguous and no-match cases are returned, what to do when the user file has problems, and how the shipped catalog remains usable. This is unusually rich behavioral context for an agent.

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?

The description is front-loaded with purpose, usage, and parameter semantics before detailing return behavior. It is lengthy, but most detail is justified because there is no output schema; the return field inventory and profile field explanation are dense but useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description covers matching semantics, all three result modes, user-file edge cases, and recommended next steps. An agent has enough information to call it correctly and interpret the response.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden for the single name parameter. It explains that the name is the model as the user says it, that case, punctuation, maker name, 'my' and 'printer' are ignored, and gives concrete equivalent examples.

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?

The description states a specific verb and resource: 'Find a 3D printer by name' in both the shipped catalog and the work folder's user printers file. It also explicitly says the tool only reads and changes nothing, which separates it from mutation-oriented siblings such as save_printer.

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?

It gives a clear trigger: use this when the user names their printer, before asking for bed size or process. It does not explicitly state when not to use it or name a competing lookup alternative, but the usage context is strong.

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