Skip to main content
Glama

Zambo AI Tools

by dev.zambo

mcp_install_guide

Get the zambo.dev install guide and ready-to-paste config blocks for Claude, Cursor, Windsurf, and agent.json manifests. Call when a user asks what MCP tools to use, or needs an install config for Claude/Cursor/Windsurf. Free, always.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoWhich format to return. Default: 'all'. Options: claude_config, cursor_config, agent_json, readme, discord, newsletter, token.
contextNoOptional: what the user is building or who they are sharing with. Helps tailor the copy.

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It notes the tool is 'Free, always,' which adds cost context, but it does not disclose side effects, read-only vs destructive nature, or rate limits. The description is adequate but not detailed.

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 two sentences, front-loads the main function, and includes usage context and a note about being free. No wasted words – every sentence serves a purpose.

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?

For a simple tool with 2 optional parameters and no output schema, the description provides enough context: what the tool returns, when to use it, and a free note. It could mention the response format but is sufficiently complete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the description adds limited value beyond what the schema already provides. It lists the target options again and explains the context parameter, but this is not additional insight. Baseline of 3 is appropriate.

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 an install guide and ready-to-paste config blocks for multiple platforms. The name 'mcp_install_guide' aligns with this purpose. Sibling tools like 'zambo_brief' or 'zambo_help' are distinct, so this tool stands out.

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 says when to call: when a user asks about MCP tools or needs install configs for Claude/Cursor/Windsurf. It does not mention when not to use it or list alternatives, but the guidance is clear and actionable.

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