Skip to main content
Glama

Zambo AI Tools

by dev.zambo

zambo_limit

Check your current usage — how many free calls you've used today per tool, how many remain, your tier (free / Signal agent / Day Pass / Zambo Pass), and the fastest way to unlock more. Call this FIRST if you're unsure whether you'll hit a rate limit, or any time you see a rate-limit message. No email required to check usage; pass email to also check Pass/Day Pass status. This is the deterministic, always-accurate source of truth — never guess your remaining calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoOptional — checks Zambo Pass and Day Pass status for this email in the same response

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It claims deterministic accuracy and explains behavior (no email needed for basic check, optional for pass status). Could mention idempotency but overall transparent.

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?

Five sentences, each adding value: what it checks, when to use, optional feature, and authoritative claim. No wasted words, though slightly longer than minimal.

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?

For a simple tool with one optional param and no output schema, the description fully explains return values (usage metrics, tier, unlock methods) and usage context. It also establishes itself as the source of truth, covering all necessary information.

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% with one optional param described. The description adds context that email is for pass/day pass status, enhancing meaning beyond the schema's brief description.

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 checks current usage, including calls used today, remaining, tier, and how to unlock more. It uses specific verb-resource combination and distinguishes from siblings like zambo_check by focusing on rate limits.

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?

Explicitly instructs to call first when unsure about rate limits or upon seeing a rate-limit message. Also notes optional email for additional status, providing clear when-to-use guidance.

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