Kong Reviews

Project stack cost over time

project_stack

Read-only

Month-by-month cost for a whole stack as users grow, with startup perks applied if requested, plus cost cliffs (forced plan upgrades, sharp jumps, credits running out). Example: {"vendors":[{"vendor_id":"supabase"},{"vendor_id":"vercel"}],"start_mau":2000,"monthly_growth":0.15,"months":24,"apply_perks":true,"founder":{"gateways":["mercury"]}}.

Input Schema

Name	Required	Description
`seats`	No	Team members on per-seat plans. Default 1.
`months`	No
`founder`	No	Optional company details used only to find startup perks.
`vendors`	Yes
`per_user`	No	Usage per active user a month, e.g. {"sms": 2, "file_storage_gb": 0.2, "ai_input_ktok": 30}. Replaces the profile and the filled-in defaults for those units; a plan's questions say which unit each answer sets. Units: mau, seat, request_million, bandwidth_gb, db_storage_gb, egress_gb, email, event, error_event, compute_hour, revenue_usd, transaction, ai_input_ktok, ai_output_ktok, kv_read, kv_write, ci_hour, file_storage_gb, file_egress_gb, file_write, file_read, video_min_stored, video_min_delivered, sms, job_run, search_request, search_record.
`start_mau`	Yes
`mau_series`	No	Explicit MAU per month; overrides start_mau, monthly_growth and months.
`per_1k_mau`	No	Override usage per 1,000 MAU. Units: mau, seat, request_million, bandwidth_gb, db_storage_gb, egress_gb, email, event, error_event, compute_hour, revenue_usd, transaction, ai_input_ktok, ai_output_ktok, kv_read, kv_write, ci_hour, file_storage_gb, file_egress_gb, file_write, file_read, video_min_stored, video_min_delivered, sms, job_run, search_request, search_record.
`profile_id`	No	Usage profile: b2b_saas (default), consumer_app, booking_marketplace, content_site, ios_on_device. Defaults to the app type's profile.
`apply_perks`	No
`monthly_growth`	No	e.g. 0.1 = 10% per month
`revenue_per_mau_usd`	No	Average monthly revenue per active user (for payment fees).
`transactions_per_mau`	No	Payments per active user per month.

Output Schema

Name	Required	Description
`data`	Yes	The tool result. Its shape depends on the tool.
`stale`	Yes
`caveats`	Yes	Show to the user word for word.
`sources`	Yes
`confidence`	Yes
`assumptions`	Yes	Usage and pricing assumptions behind the numbers.
`disclosures`	Yes	Always includes the neutrality note: no vendor pays for a place in the answer. Link its url when you mention how Kong Reviews is paid.
`generated_at`	Yes
`engine_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 26, 2026

changedInput schema / properties / per_1k_mau / description

Previous value: -"Override usage per 1,000 MAU. Units: mau, seat, request_million, bandwidth_gb, db_storage_gb, egress_gb, email, event, error_event, compute_hour, revenue_usd, transaction, ai_input_ktok, ai_output_ktok, kv_read, kv_write, ci_hour."New value: +"Override usage per 1,000 MAU. Units: mau, seat, request_million, bandwidth_gb, db_storage_gb, egress_gb, email, event, error_event, compute_hour, revenue_usd, transaction, ai_input_ktok, ai_output_ktok, kv_read, kv_write, ci_hour, file_storage_gb, file_egress_gb, file_write, file_read, video_min_stored, video_min_delivered, sms, job_run, search_request, search_record."

addedInput schema / properties / per_1k_mau / properties / file_egress_gb
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / file_read
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / file_storage_gb
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / file_write
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / job_run
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / search_record
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / search_request
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / sms
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / video_min_delivered
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```
addedInput schema / properties / per_1k_mau / properties / video_min_stored
```
Added value: +{
+  "minimum": 0,
+  "type": "number"
+}
```

addedInput schema / properties / per_user

Added value: +{
+  "additionalProperties": false,
+  "description": "Usage per active user a month, e.g. {\"sms\": 2, \"file_storage_gb\": 0.2, \"ai_input_ktok\": 30}. Replaces the profile and the filled-in defaults for those units; a plan's questions say which unit each answer sets. Units: mau, seat, request_million, bandwidth_gb, db_storage_gb, egress_gb, email, event, error_event, compute_hour, revenue_usd, transaction, ai_input_ktok, ai_output_ktok, kv_read, kv_write, ci_hour, file_storage_gb, file_egress_gb, file_write, file_read, video_min_stored, video_min_delivered, sms, job_run, search_request, search_record.",
+  "properties": {
+    "ai_input_ktok": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "ai_output_ktok": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "bandwidth_gb": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "ci_hour": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "compute_hour": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "db_storage_gb": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "egress_gb": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "email": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "error_event": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "event": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "file_egress_gb": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "file_read": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "file_storage_gb": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "file_write": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "job_run": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "kv_read": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "kv_write": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "mau": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "request_million": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "revenue_usd": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "search_record": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "search_request": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "seat": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "sms": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "transaction": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "video_min_delivered": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "video_min_stored": {
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / vendors / maxItems
```
Previous value: -12New value: +20
```

addedOutput schema / properties / disclosures / description

Added value: +"Always includes the neutrality note: no vendor pays for a place in the answer. Link its url when you mention how Kong Reviews is paid."

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / profile_id / description

Previous value: -"Usage profile: b2b_saas (default), consumer_app, booking_marketplace, content_site."New value: +"Usage profile: b2b_saas (default), consumer_app, booking_marketplace, content_site, ios_on_device. Defaults to the app type's profile."

First observedOct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: the output includes cost cliffs such as forced plan upgrades, sharp jumps, and credits expiring, which tells the agent what to expect. It does not state pagination, cost model assumptions, or currency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence front-loads the purpose well, but the trailing example dominates the length and only illustrates a subset of the 13 parameters. The raw JSON example is useful yet not the most token-efficient way to convey it; overall it's adequate but not tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex 13-parameter nested tool with an output schema, so the description must carry modeling semantics. It covers projection, growth, perks, and cliff detection, and the example anchors the vendor/founder shape. It omits how vendor plan_id/required interact with the pricing model and how per_user competes with per_1k_mau, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 69%, and the schema itself carries the rich per_unit/per_1k_mau unit lists and profile enums. The description's main contribution is a worked example showing vendors as objects with vendor_id, plus founder.gateways, which clarifies two under-documented required/nested spots. It says nothing about per_user vs per_1k_mau precedence or how apply_perks interacts with founder.existing_customer_of.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: month-by-month cost projection for a whole stack as MAU grows, plus cost cliffs. This distinguishes it from estimate_cost (point-in-time) and find_cost_cliffs (cliff-only) by combining projection + cliffs. It doesn't explicitly name those siblings, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The word 'stack' and 'as users grow' implies usage for multi-vendor growth projections, and 'with startup perks applied if requested' hints at when to set apply_perks. But there is no explicit when-to-use-this-vs-estimate_cost/find_perks/plan_stack guidance, no prerequisites, and no exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kong Reviews tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?