Skip to main content
Glama

Zambo AI Tools

by dev.zambo

zambo_compose

Run Zambo Autopilot — the 6-tool intelligence chain: ZAMBOT Spark → Zambo Score → Drift Detection → Substrate Breakthroughs → Cryptographic Chain Proof → Email Digest. The most powerful single call in the Zambo Stack. Triggers 6 tools in sequence and returns a provably-linked intelligence digest. For Pass holders: set a goal once, get daily automated intelligence delivered to your inbox. For all users: run the full chain now and get results immediately. 1 free instant run/day. Zambo Pass: daily automated runs + email delivery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYesYour strategic goal — all 6 chain tools orient around this
emailNoYour email — required for Pass holders to activate daily automated delivery
run_modeNo'now' = run the 6-tool chain immediately and return results (default) · 'set_daily' = configure as daily Autopilot goal, Zambo Pass required for daily automation

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, description carries full burden. It discloses the sequential execution of 6 tools, mentions rate limits ('1 free instant run/day'), access levels (Pass required for daily), and return format ('provably-linked intelligence digest').

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?

Six sentences, front-loaded with key action. Some marketing flair but no redundancy. Could be slightly tighter but earns its place.

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?

Given complexity (orchestration tool, no output schema), description adequately explains the chain, return value, rate limits, and access tiers. Misses details like error handling or duration but sufficient for selection.

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%, baseline 3. Description adds meaning beyond schema: 'goal' is explained as orienting the chain, 'email' tied to Pass activation, 'run_mode' clarified with defaults and Pass dependency.

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 explicitly states 'Run Zambo Autopilot — the 6-tool intelligence chain' and lists each tool, clearly distinguishing this composite tool from its individual components in the sibling list.

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?

Provides clear context for use: 'For Pass holders...' and 'For all users...', plus describes run modes ('now' vs 'set_daily'). Lacks explicit when-not-to-use guidance relative to alternatives.

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

All Zambo AI Tools 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

A3.5/5.0
Disambiguation3/5

Many tools have distinct purposes, but there are several overlapping or redundant tools (e.g., leadsignal vs leadsignal_generate, multiple code audit tools, multiple trading proposal/journal tools, and several 'universal' entry points like zambo_help, zambo_ask, zambo_universal). Descriptions help, but the volume creates ambiguity.

Naming Consistency3/5

Naming conventions vary across prefixes (zambo_, zambot_, axis_, presence_, trading_, etc.), with some tools using single words (weather, translate) and others using verb_noun patterns. Aliases like leadsignal_generate for leadsignal break consistency. While prefixes provide some grouping, the overall pattern is mixed.

Tool Count2/5

125 tools is excessive for a single MCP server, even if the server aims to be a universal stack. This makes it overwhelming for agents to navigate and increases the likelihood of misselection. Many tools could be split into domain-specific servers.

Completeness5/5

The tool surface is extraordinarily comprehensive, covering agent identity, cross-layer orchestration, code analysis, content generation, legal scanning, lead generation, trading, on-chain data, and more. Nearly any common agent task is supported with multiple tools, leaving few obvious gaps.

Resources