Skip to main content
Glama

Cabgo Builder

by app.cabgo

cabgo_install_instructions

Read-only

Use THIS for any installation / setup / connection / 'how do I connect Cabgo' question, AND for any user who says they don't have a Cabgo account yet. Returns step-by-step instructions for (a) creating a Cabgo account at https://www.cabgo.app/empezar when needed and (b) installing the Cabgo MCP connector in the user's chat client (ChatGPT, Claude Desktop, Cursor). Trigger phrases: 'how do I install', 'how do I connect', 'how do I set up the connector', 'I don't have an account', 'I'm new to Cabgo', 'cómo instalo Cabgo', 'cómo me conecto', 'cómo creo cuenta', 'connect step by step', 'add this connector'. Pass client='chatgpt'|'claude'|'cursor'|'all'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientNoDefault 'chatgpt'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

TDQS

A4.3/5.0
Behavior4/5

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

Description reveals it is a read-only instruction retrieval. Annotations show readOnlyHint=true, no contradiction. Adds details about account creation and installation steps, beyond 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?

Well-organized with bold headings and bullet-like structure. Front-loaded with key purpose. Slightly long but every sentence adds value.

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?

Covers return value, use cases, parameter, and trigger phrases. With output schema present and annotations, the description is sufficiently complete for the tool's complexity.

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?

Input schema has one parameter with enum and description. Description adds meaning by specifying default value and usage instruction ('Pass client=...'), enhancing the schema's coverage.

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 it is for installation/setup/connection questions and for users without an account. It specifies the return value (step-by-step instructions) and gives trigger phrases, differentiating it from sibling tools like pricing or account info.

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

Usage Guidelines4/5

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

Explicitly says 'Use THIS for any installation / setup / connection...', provides trigger phrases, and implies scope. Could be more explicit about when not to use, but the context is clear.

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

All Cabgo Builder toolsInspect
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