MCP: camcraft-mcp skill lists the drawn-cutter tools (get/set_tool_cutter_profile, set_tool_cutter_params)

Open
  • Is something wrong?
#1,013 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
57/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
documentation

Research direction

Read .claude/skills/camcraft-mcp/SKILL.md and compare its tool table with crates/app/src/mcp/cutter_tools.rs and the referenced PR status. Add the merged slice-2 tools and their parameters and undo note; add set_tool_cutter_params and the neck behavior note only after the referenced PRs merge. Bump .claude/PROCESS_VERSION; done also includes announcing #681 on merge.

Written by the indexing model from the issue text.

Description

area:mcp effort:low P1 source:agent

The camcraft-mcp skill (.claude/skills/camcraft-mcp/SKILL.md) has no row for the drawn-cutter MCP tools, although the live registry (tools::list(), crates/app/src/mcp/cutter_tools.rs) has them:

  • get_tool_cutter_profile and set_tool_cutter_profile, from #93 slice 2 (PR #856, merged);
  • set_tool_cutter_params {name, diameter?, corner_r?, tip_angle?, flute_len?, shank_d?, shank_len?, neck?: {diameter, length} | null}, from #93 slice 3 (PR #1012, open, merges at the next cut).

Agents driving CamCraft from the skill won't know they exist. It also matters that, since #852 (PR #957), the drawn neck feeds the collision checks and the simulation (it is no longer display only), so the skill should say so.

This is a process file, so the fix is its own small PR with a .claude/PROCESS_VERSION bump. List the slice-2 tools now; add set_tool_cutter_params once PR #1012 merges, so the table never names a tool main doesn't have.

Done means: all three tools appear in the skill's tool table with their parameters and undo note, plus the neck-feeds-the-checks note once #957 merges; PROCESS_VERSION bumped; #681 announced on merge.

Dominant language
Rust
Stars
8
Forks
11
Avg merge
5h 22m
Merged PRs (30d)
409

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NeoTech/Camcraft

All issues in NeoTech/Camcraft

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.