Skip to main content
Glama

Cabgo Builder

by app.cabgo

cabgo_get_publish_requirements

Read-only

Public (no auth): returns the REAL operator checklist for publishing (most assets are auto-generated — bundle id, screenshots, descriptions, policies — so the operator only provides API access). For Play: invite console@cabgo.app + decide update-or-new + (if updating) upload keystore. For App Store: upload the API key alone (no invitation needed). Pass platform='android'|'ios'|'both' (default both).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNoDefault 'both'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds valuable behavioral context: it's public, returns a checklist, lists auto-generated items, and gives store-specific steps. No contradiction.

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 a single paragraph that front-loads key info (public, no auth), then explains the checklist, then store-specific steps. Every sentence adds value with no waste.

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 that the tool has an output schema, the description need not explain return values. It fully explains what the tool does, including platform-specific requirements, making it complete for an agent to understand its use.

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 only parameter 'platform' is well-documented in the schema with enum and description. The description reiterates the options and default ('android'|'ios'|'both', default both), adding marginal clarity but not necessary given schema 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 the tool returns the operator checklist for publishing, distinguishes by platform (Play vs App Store), and lists auto-generated assets, making the purpose very specific and distinct from siblings.

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?

It explicitly states 'Public (no auth)' and provides platform-specific instructions, implying when to use. While it doesn't list alternatives, the context from sibling names and tool purpose is clear enough for an agent to decide.

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