Skip to main content
Glama

Zambo AI Tools

by dev.zambo

qr_generate

Generate a QR code for any URL, text, phone number, WiFi credentials, contact info, or anything else — instantly. Returns a direct image URL you can share, embed, print, or put on a flyer. Free, no auth, no limits. Examples: business website, payment link, event RSVP, WiFi password, social media profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesWhat to encode in the QR code. Can be a URL, text, phone number, email, WiFi config, vCard, or any string.
sizeNoSize in pixels (square). Default: 400. Max: 1000.

TDQS

A4.3/5.0
Behavior4/5

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

Discloses 'Free, no auth, no limits' and that it returns a direct image URL, but does not mention error handling or edge cases; however, no annotations exist, so description carries full burden and does well.

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 sentences with front-loaded purpose, no wasted words, highly efficient.

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 simple tool with only 2 params and no output schema, description fully covers purpose, output, usage examples, and constraints.

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 coverage is 100% and both parameters are described. Description adds context about data types but does not significantly enhance schema meaning beyond what is already provided.

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?

Description clearly states it generates QR codes for various data types (URL, text, WiFi, etc.), using specific verb 'generate' and resource 'QR code', and distinguishes from sibling tools as it's the only QR-related tool.

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 examples of use cases (business website, payment link, etc.) but does not explicitly mention when not to use or alternative tools, though context makes it clear.

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