AgentStack MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRICE_PRO | No | Price for the Pro plan (optional, used for billing). | |
| AGENTSTACK_KV | No | Cloudflare KV namespace binding for billing quota storage (optional). | |
| PRICE_STARTER | No | Price for the Starter plan (optional, used for billing). | |
| STRIPE_SECRET_KEY | No | Stripe secret key for billing endpoints (optional, used on paid plans). | |
| AGENTSTACK_PROFILE | No | Profile to load a subset of tools (e.g., 'all', 'finance', 'decision', 'simulation'). Defaults to 'all'. | all |
| STRIPE_WEBHOOK_SECRET | No | Stripe webhook secret for validating webhook events (optional). |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_capabilitiesB | Discovery: namespaces (sim_*, decide_*, calc_*), composite tools, and profiles. |
| health_checkB | Aggregated health for the whole stack. |
| sim_runC | SIMULATE. Deterministic what-if projection from a template or free-form 'metrics' model. |
| sim_sensitivityC | SIMULATE. Vary scenario inputs and show impact on a target metric. |
| sim_break_evenC | SIMULATE. Solve for the input value that makes a metric hit a target. |
| sim_compareC | SIMULATE. Compare 2-3 scenarios side by side. |
| sim_list_templatesA | SIMULATE. List every scenario template with inputs and outputs. |
| decideA | DECIDE. Rank options against weighted criteria; returns winner, ranking, breakdowns, explanation. |
| decide_scoreC | DECIDE. Full normalized scored matrix + ranking. |
| decide_sensitivityC | DECIDE. Robustness of the winner to CRITERIA-WEIGHT changes. |
| decide_compare_twoC | DECIDE. Head-to-head between exactly two options. |
| decide_list_methodsB | DECIDE. List scoring methods. |
| calc_metricC | COMPUTE. Exact business/SaaS/finance metric (ltv, cac, rule_of_40, nrr, ...). |
| calc_list_metricsB | COMPUTE. List supported metrics + schemas. |
| calc_currency_convertC | COMPUTE. Convert currencies with Decimal precision. |
| calc_business_daysC | COMPUTE. Business-day arithmetic with holidays. |
| calc_compound_growthD | COMPUTE. future_value | present_value | cagr. |
| calc_npvC | COMPUTE. Net Present Value. |
| calc_irrC | COMPUTE. Internal Rate of Return. |
| calc_loan_amortizationC | COMPUTE. Level-payment loan schedule. |
| calc_depreciationD | COMPUTE. Depreciation schedule. |
| plan_to_valuationC | COMPOSITE (simulate -> compute). Project a scenario, value its cash-flow line (NPV/IRR). |
| evaluate_options_with_scenariosC | COMPOSITE (simulate -> decide). Project each option, rank the outcomes. |
| stress_test_decisionC | COMPOSITE (simulate x decide). Stress a scenario assumption and see if the winner holds. |
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 24 tools
Most tools are cleanly separated by domain prefixes (sim_, decide_, calc_) with distinct actions. However, decide and decide_score have overlapping outputs, and calc_metric overlaps conceptually with specific calc_npv and calc_irr tools, creating potential confusion.
Domain prefixes give structure, but the suffixes mix verbs and nouns inconsistently (sim_run vs sim_sensitivity, calc_metric vs calc_list_metrics). Composite tools use a completely different naming style, breaking the pattern.
At 24 tools, the server is on the heavy side, but the three domains each justify several tools. Some redundancy (decide vs decide_score) could reduce the count, making it borderline.
Core workflows for simulation, decision, and calculation are well covered, including composite tools that span domains. Minor gaps exist, such as no way to create or edit scenario templates and no persistence for decisions, but these are not critical.