Cabgo Builder

cabgo_pricing

Read-only

Public (no auth): informational pricing reference. Returns monthly SaaS subscriptions (Basic $15 / Professional $30 / Enterprise $70 per month, which INCLUDE 300 / 1,000 / 3,500 trips per month; trips above that quota are billed at $0.05 / $0.03 / $0.02 each — the monthly price is a floor, never quote it alone to an operator who has volume) and one-time app-build packages (Starter $399 Android-only, Pro $699 Android+iOS, Full $999 Android+iOS+source code). All plans include unlimited drivers / users / admins; Cabgo never takes a commission on the fare (the per-trip overage above is a quota charge, not a commission). Informational only. Do not generate or return a payment URL from this tool. When the operator wants to purchase, direct them to visit https://www.cabgo.app/empezar in their browser — all checkout happens on cabgo.app externally via Stripe, not inside this conversation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "data": {}
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedJun 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description reveals that the tool requires no authentication and is non-destructive, consistent with annotations. It also clarifies that it never returns a payment URL and that checkout happens externally, adding behavioral context beyond the readOnlyHint.

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?

The description is detailed but well-organized, leading with the purpose and then listing pricing tiers, overage charges, and purchase instructions. Every sentence adds necessary information without redundancy.

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

Completeness5/5

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

The description covers all essential aspects: pricing details, quota overage, commission clarification, and purchase routing. It also differentiates from siblings and explains the tool's limitations, making it complete for an agent to use correctly.

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

Parameters4/5

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

The tool has zero parameters, so there is no input schema to explain. The description provides a baseline of clarity, which meets the expected level for a parameterless tool.

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?

The description states it is a 'Public (no auth): informational pricing reference' that returns monthly SaaS subscriptions and one-time app-build packages. It clearly distinguishes itself from sibling tools by emphasizing it is informational only and not a purchasing tool.

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

Usage Guidelines5/5

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

It explicitly says 'Informational only' and directs users to visit an external URL for purchase, while also warning not to quote the monthly price alone to operators with volume. This provides clear guidance on when to use this tool versus alternatives like cabgo_start_signup or cabgo_create_my_app.

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

All Cabgo Builder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?