Tool Reference: Projects & Calcs
MCP tools to list, read, create, and update projects and calculations.
These are the tools Claude uses to find your work and create new calcs. They mirror the web app exactly — anything created or edited here shows up immediately in ClearSpan, scoped to your firm. You normally don't call these by name; you ask Claude in plain language and it picks the right tool.
Project tools#
| Tool | What it does | Key arguments |
|---|---|---|
list_projects | Lists projects in your firm, most-recently-updated first | limit (1–100, default 20), search (matches name, address, project number) |
get_project | Returns one project's details | project_id |
create_project | Creates a new internal project in your firm | name (required); optional project_number, address, company, construction_type |
For create_project, construction_type (when given) must be either new_construction or remodel. A project number you pass is stored as the firm's internal reference number.
Tools are firm-scoped. list_projects only returns projects you can already see in the web app, and every read or write re-checks that you're still an authorized org member.
Calc tools#
| Tool | What it does | Key arguments |
|---|---|---|
list_calcs | Lists calculations in a project | project_id |
get_calc | Returns one calc including its full params blob | calc_id |
create_wood_beam_calc | Creates a wood beam calc (NDS engineer flow) | project_id, name, span_ft, member, load_patterns, load_combos, load_cases, optional deflection_limits |
update_wood_beam_calc | Edits a wood beam calc in place (partial) | calc_id plus any fields to change |
create_wood_post_calc | Creates a wood post (column) calc | project_id, name, geometry, optional member, and either load_cases or reaction_source |
update_wood_post_calc | Edits a wood post calc in place (partial) | calc_id plus any fields to change |
save_beam_design_calc | Persists a simple-span beam analysis as a calc | project_id, name, analysis_input (from design_beam) |
Creating wood calcs#
create_wood_beam_calc makes a real calculation in the project — identical to creating one in the web UI. A member section is required to run or report, but you can create the calc without one and let the solver suggest candidates. See Runners for the solve step and section sweep.
For create_wood_post_calc, provide axial loads in exactly one of two ways:
- Manual demands — pass
load_cases(a list of axial cases withP_kipsand an NDSduration_type). - Linked from a beam — pass
reaction_sourcepointing at a solved wood-beam calc; the post's loads are derived from that beam's reactions, and the link is stored so a later run re-derives from the beam's current reactions. See Link Loads to a Calc.
Editing in place#
update_wood_beam_calc and update_wood_post_calc are partial updates: pass only the fields you want to change. member and geometry are merged into the existing values (so you can swap just the section), while load_patterns, load_combos, load_cases, and deflection_limits replace their list wholesale.
Editing any design field clears the cached results. Run the calc again with the matching runner to re-solve before generating a report. Engineer/MCP calcs are not gated by status — there's no draft/submitted restriction on editing.
Simple-span beam analysis#
save_beam_design_calc persists the output of the design_beam analyzer. Pass the analysis_input returned by design_beam verbatim so the saved calc round-trips back through the Beam Design Analysis page. The analyzer itself is documented in Runners.
Related#
- Runners — solve calcs and read results.
- Load Criteria — derive applied loads from project design loads.
- Wood Beam Calcs and Wood Post Calcs — the web-app equivalents.