Skip to main content
Glama

Cabgo Builder

by app.cabgo

cabgo_about

Read-only

Public (no auth): describe what Cabgo is. Returns the full product catalog — what kinds of apps an operator can launch, pricing, who Cabgo is for, and how to onboard. Use ONLY when the user explicitly asks what Cabgo is, what it does, or wants an overview. Do NOT call this as a pre-step before cabgo_create_my_app — when the user wants to create / launch an app, go directly to cabgo_create_my_app without fetching context first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=true), the description adds 'Public (no auth)' and states it returns the full product catalog. No contradictions with annotations, and it provides useful behavioral context.

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 concise—two sentences plus a strong warning—with no wasted words. It front-loads the core purpose and includes critical usage guidance.

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 zero parameters and an output schema (implied), the description is complete. It covers the tool's purpose, target audience, return value, and circumscribes its use in relation to sibling tools.

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

Parameters5/5

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

The input schema has zero parameters (empty object). Although no parameter descriptions are needed, the description effectively explains what the tool returns, which fully compensates. Baseline 4 is satisfied; the description adds context beyond 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 what the tool does: describes Cabgo, returns the full product catalog, and specifies conditions for use. It distinguishes itself from sibling tools like cabgo_create_my_app by explicitly stating when NOT to call it.

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 usage guidelines: 'Use ONLY when the user explicitly asks what Cabgo is' and 'Do NOT call this as a pre-step before cabgo_create_my_app'. This clearly delineates when and when not to use the tool.

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