Zambo AI Tools

zambo_session

Load a ZAMBO session — instantly resume your exact context from Telegram, web, or any previous session in this AI client. Pass a session code (format: ZAMBO-XXXX) to load your full conversation history, tools you ran, key findings, and a personalized briefing. Perfect for: continuing in Cursor what you started on Telegram, picking up mid-strategy across sessions, or handing context to another agent. Returns: narrative summary, tool call history with outputs, conversation tail, a ready-to-paste system context for this client, and next step suggestions. To get a session code: use ZAMBO Bot on Telegram (t.me/zambodev_bot) and run /export. Free, no auth required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	Session code from ZAMBO Bot /export command. Format: ZAMBO-XXXX (e.g. ZAMBO-K7M2). Case insensitive.

TDQS

A4.4/5.0

Behavior4/5

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

No annotations provided, but the description discloses key behaviors: 'instantly resume', returns narrative summary and tool history, and states 'Free, no auth required.' It implies a read-only operation without mentioning destructive effects, which is appropriate.

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?

The description is well-structured with a clear opening, explanation of returns, use cases, and how to obtain the code. It is slightly lengthy but every sentence adds necessary context; no redundancy.

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 the single parameter and no output schema, the description fully covers what the agent needs: input format, output contents, use cases, and prerequisites. No gaps remain.

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 a clear parameter description. The description adds value by explaining the source of the session code and format details, going beyond the schema's basic 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 'Load a ZAMBO session' with a specific verb and resource. It explains what the tool does (resume context from previous sessions) and differentiates from siblings like 'zambo_recall' by focusing on session codes and cross-platform continuity.

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?

The description explicitly lists use cases ('continuing in Cursor... picking up mid-strategy... handing context to another agent') and tells how to obtain a session code via Telegram. It does not explicitly state when not to use, but the context is clear enough.

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 tools Inspect

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

Need Help?