Zambo AI Tools

presence_session_attach

Attach real browser session cookies to a Presence identity, enabling authenticated actions. Export cookies from DevTools → Application → Cookies → copy as JSON array [{name,value,domain,path},...]. Cookies are encrypted with AES-256-GCM before storage. CALL FORMAT: presence_session_attach({ identity_id: 'uuid', cookies_json: '[{...}]', user_agent: 'Mozilla/...' })

Input Schema

TableJSON Schema

Name	Required	Description
`user_agent`	No	Browser user-agent string (optional).
`identity_id`	Yes	UUID of the identity to attach cookies to.
`cookies_json`	Yes	JSON array of cookie objects from DevTools.

TDQS

A4.3/5.0

Behavior4/5

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

Discloses that cookies are encrypted with AES-256-GCM before storage, which is a critical security detail. No annotations present, so description carries the burden. Could add information about reversibility or failure modes.

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?

Two concise sentences plus a formatted call example. Every sentence adds unique value: purpose, prerequisite instructions, encryption detail, and call format. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no description of what the tool returns (success/failure, attached session info). For a mutation tool, knowing the response is important. Otherwise, the description covers purpose, usage, and security adequately.

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% (3 parameters all have descriptions). The description adds value by showing the exact JSON array format for cookies and providing a sample call with real values, which helps the agent understand the expected structure.

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?

Specific verb 'Attach' and resource 'real browser session cookies to a Presence identity' clearly state the tool's action. Distinguishes from sibling tools like presence_session_create which manage sessions at a different level.

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 explicit step-by-step instructions for exporting cookies from DevTools and a call format example. However, does not mention when to use this tool versus other presence tools like presence_session_create or presence_session_kill.

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?