SCModeling
Server Details
Supply-chain network design via simulation, optimization, and greenfield analysis.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.5/5 across 11 of 11 tools scored.
Tools are cleanly separated into three domains (greenfield, optimization, simulation) with distinct purposes. Each domain has list, describe, get, and explain variants that are clearly differentiated by their prefixes and descriptions.
All tool names follow a consistent verb_noun pattern using underscore_case. Verbs like list_, describe_, get_, explain_, run_ are used uniformly across domains, making the naming predictable.
11 tools is well-scoped for a supply chain modeling server covering three main areas. Each area has a minimal but complete set of operations (list, describe, get, explain) without superfluous tools.
The tool surface covers the full lifecycle for sample demos: listing available demos/models, getting details, retrieving precomputed results, and explaining underlying concepts. No obvious gaps in functionality for the server's stated purpose.
Available Tools
11 toolsdescribe_greenfield_demoRead-onlyIdempotentInspect
Full detail on one greenfield demo — region, customer count, available dc_count values, and the score-curve elbow finding. Use this before get_greenfield_result to know what dc_count values are precomputed.
| Name | Required | Description | Default |
|---|---|---|---|
| demo_id | Yes | Which greenfield demo to describe |
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
describe_opt_demoRead-onlyIdempotentInspect
Full detail on one optimization demo — controls, available scenario keys, sites, fixed parameters, citations, and the key finding the demo illustrates. Use this before get_opt_result to know what scenario_key values are accepted.
| Name | Required | Description | Default |
|---|---|---|---|
| demo_id | Yes | Which optimization demo to describe |
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
explain_greenfieldRead-onlyIdempotentInspect
Reference text on greenfield analysis — clean-slate facility-location math. Covers the weighted center-of-gravity (Weber) formulation, Weiszfeld's iterative algorithm, Lloyd's-style alternating location-allocation for N facilities, service constraints (% demand vs % customers within a distance band), and the inverse problem of solving for minimum N. Also covers when to use greenfield vs facility selection (the open/close MIP). Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does greenfield analysis work' or 'where would I put my DCs' question. ChiAha's GreenfieldAnalysis engine powers the US Greenfield Design demo on the sandbox.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
explain_optimizationRead-onlyIdempotentInspect
Reference text on supply-chain network optimization — mixed-integer programming (MIP), the structure of decision variables and constraints, the objective function for landed-cost minimization, and the common problem classes (facility selection, sourcing, flow constraints, multi-period, BOM/production, multi-objective). Also covers when to reach for optimization vs simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does network optimization work' question. ChiAha's AMOS optimizer (open-source, Odin, GLOP/CBC via OR-Tools) powers the Tariff and Coffee Co-pack demos on the sandbox.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
get_greenfield_resultRead-onlyIdempotentInspect
Get the precomputed result for one DC count of a greenfield demo. Returns sited DCs (lat/lon + city/state, nearest-city snapped), customer-to-DC assignments, and the score for that DC count. ANTI-FABRICATION: every result is verbatim engine output from greenfield-cli — quote them in your reply, do not round or fabricate cities.
| Name | Required | Description | Default |
|---|---|---|---|
| demo_id | Yes | Which greenfield demo | |
| dc_count | Yes | Number of DCs to site (2-8) |
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
get_opt_resultRead-onlyIdempotentInspect
Get the precomputed result for one scenario of an optimization demo. Returns the verbatim engine output JSON (AMOS for tariff/coffee, SSO output for sso-basic) including the optimal sourcing/production/transport decisions, costs, and any open/close facility variables. ANTI-FABRICATION: every numeric result is verbatim from the optimization engine that ran offline — quote them in your reply, do not round or recompute. Call describe_opt_demo first to learn valid scenario_key formats for each demo.
| Name | Required | Description | Default |
|---|---|---|---|
| demo_id | Yes | Which optimization demo | |
| scenario_key | No | Scenario key within the demo. Format varies per demo — call describe_opt_demo for the exact valid keys before guessing. Tariff uses 'APAC=<N>' where N is one of 0, 7.5, 25, 50, 100. Coffee uses '<configKey>|DSL=<N>' where configKey is T/TA/TS/TAS and N is 20-70 in steps of 5 (10c units of $/gal). sso-basic is single-scenario; scenario_key is ignored. |
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
get_sc_theoryRead-onlyIdempotentInspect
Reference guide to supply-chain simulation concepts: ordering policies, BOM, FDD formulas, event-driven simulation. Pure static text — no engine call, deterministic output. Use this when the user asks a conceptual 'how does this work' question rather than asking for a number.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
list_greenfield_demosRead-onlyIdempotentInspect
List the bundled SCModeling greenfield demos. Returns id + label + one-line summary. Currently one demo (US, 189 customer points). Use this before describe_greenfield_demo or get_greenfield_result.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
list_modelsRead-onlyIdempotentInspect
List the bundled SCModeling sample supply-chain models. Returns a catalog with each model's id and a short description. Use this before run_simulation to know which model_id values are valid.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
list_opt_demosRead-onlyIdempotentInspect
List the bundled SCModeling optimization demos. Returns id + label + one-line summary for each (Tariff, Coffee Co-pack, SSO Basic). Use this before describe_opt_demo or get_opt_result to know which demo_id values are valid. All demos are precomputed sample-only fixtures — for optimization on real client data, the SCModeling desktop tool is the product.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| content | No | MCP content blocks — single text block with the response body |
run_simulationRead-onlyInspect
Run a supply-chain simulation on a bundled SCModeling sample model (sdi-db). Returns metrics, inventory time-series, orders, shipments, routing and BOM. ANTI-FABRICATION: the returned numbers come from a real discrete-event simulation run on the sc-sim engine. Quote them VERBATIM in your reply. Do not round, estimate, average, or compute derived figures from training-data recall. If the user asks a follow-up about the same model, re-call this tool rather than recalling numbers from earlier in the conversation.
| Name | Required | Description | Default |
|---|---|---|---|
| model_id | Yes | Which sample model to simulate |
Output Schema
| Name | Required | Description |
|---|---|---|
| details | No | Full run detail: config, locations, materials, routing, demands, orders, shipments, inventory_timeseries |
| metrics | No | Top-line scalar KPIs (orders, shipments, simulation_days) |
| metadata | No | Model name, version, timestamp |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!