Skip to main content
Glama

Kong Reviews

by com.kongreviews
OverviewDiscussionsAdmin

Compare vendors in a category

compare_vendors
Read-only

Rank vendors in one category at a given scale. Vendors meeting every must-have come first, then cheapest. Ranking is by cost and fit only. Example: {"category":"auth","mau":50000,"requirements":[{"capability":"auth.saml_sso"}]}.

Input Schema

NameRequiredDescriptionDefault
mauYes
seatsNoTeam members on per-seat plans. Default 1.
excludeNo
categoryYes
per_userNoUsage 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.
per_1k_mauNoOverride 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_idNoUsage profile: b2b_saas (default), consumer_app, booking_marketplace, content_site, ios_on_device. Defaults to the app type's profile.
requirementsNo
revenue_per_mau_usdNoAverage monthly revenue per active user (for payment fees).
transactions_per_mauNoPayments per active user per month.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result. Its shape depends on the tool.
staleYes
caveatsYesShow to the user word for word.
sourcesYes
confidenceYes
assumptionsYesUsage and pricing assumptions behind the numbers.
disclosuresYesAlways 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_atYes
engine_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "hosting",
-  "database",
-  "auth",
-  "email",
-  "payments",
-  "observability",
-  "ai",
-  "edge",
-  "app_store",
-  "coding"
-]New value: +[
+  "hosting",
+  "database",
+  "auth",
+  "email",
+  "payments",
+  "observability",
+  "ai",
+  "edge",
+  "app_store",
+  "coding",
+  "storage",
+  "video",
+  "sms",
+  "push",
+  "jobs",
+  "search"
+]
    • 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 / requirements / items / properties / categories / items / enum
      Previous value: -[
-  "hosting",
-  "database",
-  "auth",
-  "email",
-  "payments",
-  "observability",
-  "ai",
-  "edge",
-  "app_store",
-  "coding"
-]New value: +[
+  "hosting",
+  "database",
+  "auth",
+  "email",
+  "payments",
+  "observability",
+  "ai",
+  "edge",
+  "app_store",
+  "coding",
+  "storage",
+  "video",
+  "sms",
+  "push",
+  "jobs",
+  "search"
+]
    • 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."
  2. Changed3 schema fields changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "hosting",
-  "database",
-  "auth",
-  "email",
-  "payments",
-  "observability",
-  "ai",
-  "edge",
-  "app_store"
-]New value: +[
+  "hosting",
+  "database",
+  "auth",
+  "email",
+  "payments",
+  "observability",
+  "ai",
+  "edge",
+  "app_store",
+  "coding"
+]
    • 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."
    • changedInput schema / properties / requirements / items / properties / categories / items / enum
      Previous value: -[
-  "hosting",
-  "database",
-  "auth",
-  "email",
-  "payments",
-  "observability",
-  "ai",
-  "edge",
-  "app_store"
-]New value: +[
+  "hosting",
+  "database",
+  "auth",
+  "email",
+  "payments",
+  "observability",
+  "ai",
+  "edge",
+  "app_store",
+  "coding"
+]
  3. First observed

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 safety is covered. The description adds genuinely useful ranking behavior — must-haves first, then cheapest, 'cost and fit only' — but leaves unstated what happens with nice-to-have requirements (must:false), what an empty/no-match result looks like, and whether ranking is stable across identical costs.

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

Conciseness4/5

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

Front-loaded with the core operation and ranking rule in two sentences, then a compact example. Slight redundancy between 'then cheapest' and 'ranking is by cost and fit only', but nothing is padded.

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

Completeness3/5

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

An output schema exists, so return values needn't be described. But with 10 parameters, two nested override objects, and a profile system that interacts with per_user/per_1k_mau defaults, the description does not explain how those overrides layer. It is adequate for the common call and thin for the advanced ones.

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%, so roughly half the parameters are documented in the schema and several (category, mau, exclude) are bare. The single example clarifies the shape of the requirements objects and how category/mau combine, but says nothing about profile_id, per_user, per_1k_mau, seats, or exclude, which are the highest-complexity inputs. Partial compensation only.

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 and resource with scope: 'Rank vendors in one category at a given scale.' That is clearly distinct from siblings like check_fit, estimate_cost, or list_vendors, which either evaluate a single stack or enumerate data. It stops short of naming those alternatives explicitly, but the operation is unambiguous.

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?

Use is implied by the ranking/scoping language and the sample call, but there is no explicit when-to-use or when-not, and no routing to close siblings such as check_fit (single stack fit) or recommend_stack. An agent must infer which of these to reach for.

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

All Kong Reviews toolsInspect
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