mto-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diff_mto_scsaA | Compare an MTO file against a Plant 3D SCSA export. Read-only - never writes anything. Returns counts and item lists for the 3 scenarios: qty_mismatch, removed (in MTO, not in SCSA anymore), new (in SCSA, not yet in MTO). Items with matching qty in both are counted in summary.matched but not listed individually. Args: mto_path: path to the MTO .xlsx file. scsa_path: path to the SCSA .xlsx export. category: optional filter - one of pipe/elbow/tee/reducer/flange/ valve/blind_flange/gasket/stud_bolt/bolt/nut/washer/ gate_valve/safety_valve/ball_valve/steam_trap/pipe_support/ insulation/structural_steel. Omit to diff everything. |
| apply_mto_updateA | Write the MTO/SCSA reconciliation into the MTO file. Always re-derives the diff from the two paths (never trust a caller-supplied diff blob). Quantity corrections and new items are applied whenever dry_run=False - they're additive/corrective, not destructive. Removals (zeroing a quantity because the item left the project) are ONLY written when include_removals=True as well. Recommended flow: call with dry_run=True first to preview writes, then call again with dry_run=False, and include_removals=True only once you've reviewed the removed list. Args: mto_path: path to the MTO .xlsx file to update. scsa_path: path to the SCSA .xlsx export (source of truth). category: optional category filter, same as diff_mto_scsa. include_removals: if True, zero out items no longer in SCSA. dry_run: if True, compute and report but write nothing. output_path: write to a different file instead of overwriting mto_path. Defaults to overwriting mto_path in place. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: diff_mto_scsa is explicitly read-only comparison, while apply_mto_update is write-back with dry-run and removal safeguards. There is no realistic ambiguity about which tool to select for a given task.
Both names follow a consistent verb_noun snake_case pattern: diff_mto_scsa and apply_mto_update. The shared 'mto' prefix ties them to the same domain, and the verbs clearly signal read vs. write actions.
Two tools is slightly below the typical 3-15 range, but this is a deliberately narrow reconciliation workflow where diff and apply are exactly the needed operations. The small count is reasonable and neither tool is redundant.
The server covers the full diff-then-apply lifecycle: it can identify mismatches, removed items, and new items, and then safely write corrections back, including controlled removal handling. Parametrized categories, dry-run preview, and output_path prevent dead ends.