Bidsketch MCP by usefulapi

The resource+action naming plus explicit descriptions ("it is not added to any proposal", "changes the proposal's price") cleanly separate account-level reusable entities from per-proposal lines. The only real risk is the create/add vs. update/add near-pairs (create_fee vs add_proposal_fee, update_fee vs update_proposal_fee), where an agent must read carefully to know whether it is editing a saved library item or a specific proposal's line.

Every tool is prefixed bidsketch_ and follows a strict verb_noun snake_case pattern (list_/get_/create_/update_/add_ + resource). The add vs. create distinction is applied systematically (add = attach to a proposal, create = save reusable), so deviations are meaningful rather than arbitrary.

29 tools is heavy by raw count, but the surface covers CRUD across seven entities (clients, proposals, proposal fees, proposal sections, reusable fees, reusable sections, templates), so most tools genuinely earn their place. It is still borderline bloated for a niche proposal tool, and folding read operations or trimming library entities would keep it under ~20.

Read/write coverage for clients, proposals, fees, sections and templates is broad and thoughtful, but there are no delete/remove operations anywhere (no delete_client, delete_proposal, delete_fee, remove proposal fee) and no way to send a proposal or change its status, leaving a draft-creation dead end. Templates are also read-only, so template lifecycle management is missing.