Kong Reviews

Find cost cliffs

find_cost_cliffs

Read-only

Scan a range of user counts for one vendor and report where cost jumps: forced plan upgrades and points where usage charges start. Example: {"vendor_id":"clerk","from_mau":1000,"to_mau":200000}.

Input Schema

Name	Required	Description
`seats`	No	Team members on per-seat plans. Default 1.
`to_mau`	No
`from_mau`	No
`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.
`required`	No
`vendor_id`	Yes
`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.
`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.

Changed13 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"
+}

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

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral value by specifying what it reports (forced plan upgrades, points where usage charges start), which goes beyond the annotations. It stops short of detailing computational cost or how discontinuous ranges are sampled.

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

Conciseness5/5

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

Two sentences: purpose is front-loaded, and the example immediately grounds the abstract 'range of user counts' in concrete parameters. No filler or repetition.

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?

An output schema exists and the nested per_user/per_1k_mau semantics are well documented in-schema, so the description needn't restate returns. For a 10-param nested tool it covers purpose and range well, though the profile-vs-per_user-vs-per_1k_mau relationship is left entirely to the schema.

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 60%, and the example concretely illustrates from_mau/to_mau, which are undocumented in the schema itself. But the description says nothing about the interaction among profile_id, per_user, per_1k_mau, seats, and required, leaving the more complex nested override parameters to the schema alone.

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

Purpose5/5

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

States a specific verb and resource (scan a range of user counts for one vendor) and precisely what it outputs: forced plan upgrades and points where usage charges start. This crisply distinguishes it from the generic estimate_cost/project_stack siblings by focusing on discontinuities rather than a single cost figure.

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 scope 'scan a range of user counts for one vendor' implies when to use it (to locate cliff points), and the from_mau/to_mau example reinforces the range concept. However, it never names an alternative such as estimate_cost or says when not to use this versus a single-point estimate, leaving the sibling choice to inference.

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?