Cabgo Builder

cabgo_create_my_app

Materializes a free Cabgo workspace for the operator and queues an Android build of their branded app. No payment, no card, no checkout — the workspace is free to create and operate. Call ONLY when the user explicitly wants to create / launch / spin up / set up a new app for their business — verbs like 'create', 'launch', 'build me', 'set up an app for'. Do NOT call this for setup / installation / connector questions (use cabgo_install_instructions). Ask the user 2 things: (1) what type of business — taxi / food delivery / gas distribution? (2) what brand name for their app? Optionally city + brand color. The connected OAuth user becomes the owner automatically — no email or name is needed in the body. A single user can own multiple tenants — calling this again creates a NEW workspace rather than erroring. Branding tweaks happen via other Cabgo tools after creation. Any plan / billing / subscription management is done by the operator on https://www.cabgo.app — never through this tool.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Operator's city. Stored as context — operator adjusts the zone after first login.
`country`	No	ISO 3166-1 alpha-2 lowercase. Default 'mx'.
`brandName`	Yes	App brand shown to riders. e.g. 'Rappi Express', 'Taxi del Valle'.
`businessType`	Yes	taxi = transport; delivery_food = restaurants; delivery_gas = LP gas distribution.
`primaryColor`	No	Hex color. Defaults to a sensible per-vertical palette (blue/red/orange).
`ownerWhatsApp`	No	WhatsApp in +E.164 (optional, for reminder messages).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

The description adds context beyond annotations: it is a free workspace creation with no payment needed, the OAuth user becomes owner automatically, a single user can own multiple tenants (calling again creates new workspace), and branding tweaks occur via other tools. No contradiction with annotations.

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?

The description is well-structured and each sentence adds value, but it is slightly lengthy. It front-loads the main action and free-ness, then provides usage guidance and behavioral notes. Could be tightened slightly, but no fluff.

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?

Given the 6 parameters, output schema, and annotations, the description covers purpose, usage guidelines, behavioral traits, and parameter hints comprehensively. It provides sufficient context for the agent to correctly invoke the tool.

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?

Schema coverage is 100%, providing a baseline of 3. The description adds value by explaining enum meanings (taxi=transport, etc.), providing brandName examples, noting country default, and explaining that city is stored as context. This enhances understanding beyond the schema.

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 clearly states the tool materializes a free Cabgo workspace and queues an Android build, using specific verbs like 'create', 'launch', 'build me', 'set up an app for'. It distinguishes from siblings like cabgo_install_instructions by specifying when not to call.

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?

The description provides explicit guidance on when to call (only when user explicitly wants to create/launch), when not to call (for setup/installation, use cabgo_install_instructions), and what to ask the user (business type, brand name). It also mentions alternatives for branding tweaks and billing.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a distinct purpose: about, create app, create trial, publish requirements, install instructions, pricing, and signup. Even though cabgo_create_my_app and cabgo_create_trial both create tenants, their descriptions clearly differentiate them by context (free workspace vs trial) and intended use (immediate app creation vs trial configuration).

Naming Consistency4/5

All tools use the 'cabgo_' prefix consistently and mostly follow a verb_noun pattern (e.g., create_my_app, create_trial, get_publish_requirements). Two tools (cabgo_about, cabgo_pricing) are nouns rather than verbs, but this is a minor deviation that does not hinder comprehension.

Tool Count5/5

With 7 tools, the server is well-scoped. The count is sufficient to cover the core onboarding workflow without being overwhelming or insufficient for the stated purpose of helping users launch and publish their app.

Completeness3/5

The tool set covers the initial lifecycle (info, creation in two modes, publishing requirements, installation, pricing, and legacy signup). However, there are no tools for post-creation management (e.g., updating app settings, managing drivers, viewing analytics), which leaves notable gaps for ongoing operations.

Resources

Need Help?