Skip to main content
Glama
Sign In
AutoManus MCP Server

AutoManus MCP Server

Official
by automanus-io
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

generate_qr_code

Generate a QR code image URL for any URL or WhatsApp link. Specify a phone number and optional message for WhatsApp QR codes.

Instructions

Generate a QR code for a URL or WhatsApp link. Returns a URL to the QR code image that can be opened in a browser or downloaded.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoDirect URL to encode in the QR code (e.g., https://example.com)
phoneNoWhatsApp phone number with country code, no + sign (e.g., 16506053956). Used if url is not provided.
messageNoPre-filled WhatsApp message text. Used with phone parameter.
sizeNoQR code size in pixels (100-1000, default 300)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.6

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool returns a URL to the image, implying no side effects, but does not explicitly clarify that it is read-only or stateless, nor mention rate limits or authorization.

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, no wasted words, front-loaded with purpose and return type.

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?

Given no output schema, the description should clarify parameter relationships (e.g., url vs phone+message). It does not, and size parameter is omitted. Fairly complete for a simple tool but with gaps.

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% with descriptions for each parameter. The description adds context about URL vs WhatsApp usage but does not significantly augment the schema's meaning. Baseline score 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 it generates a QR code for a URL or WhatsApp link and returns a URL to the image. This distinguishes it from siblings like add_knowledge and create_sales_agent, which are unrelated.

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 implies its use for QR code generation, but provides no explicit guidance on when to use or not use it, nor alternatives. However, siblings are unrelated, so minimal guidance is acceptable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools