Skip to main content
Glama

Zenn logo maker

Make logos with Zenn

make_logos
Read-only

Design logo ideas for a business name with Zenn, the AI logo maker and brand kit builder. Use it when someone wants a logo, logo ideas or a brand for a business, shop, channel or project. Returns live logo designs for the name plus links to customise and download the logo and a full brand kit (business cards, social media kit, brand guide).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe business or brand name to put in the logo, exactly as it should be written.
industryNoWhat the business does, in a few words, e.g. bakery, plumber, gaming channel, law firm, skincare brand.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context that annotations cannot express: it returns live logo designs for the name plus links to customise and download, and a brand kit spanning business cards, social media, and a brand guide. The only soft spot is the tension between openWorldHint=false and a tool that fetches live designs, which is never reconciled.

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?

Three sentences, front-loaded with the action and then the trigger and return values. Every sentence carries distinct information — capability, when to use, what comes back — with no filler or repetition of the title.

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 two-parameter, non-destructive generation tool with no output schema, the description is nearly self-sufficient: it explains both the inputs' intent and the shape of the result. Missing only secondary operational details such as whether generation requires an account, whether results are billed, or how long links remain valid.

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%, so both `name` and `industry` are already documented in the schema with good examples. The description reinforces the business-name framing and mentions the surrounding brand kit but adds no formatting rules, length limits, or guidance on when `industry` matters. Baseline 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 opens with a specific verb and resource — "Design logo ideas for a business name with Zenn" — and names the underlying engine (AI logo maker and brand kit builder). It is immediately clear what the tool produces, so an agent can distinguish it from any brand-adjacent utility without opening the schema.

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?

It gives an explicit trigger: "Use it when someone wants a logo, logo ideas or a brand for a business, shop, channel or project." That covers the main intent variants and the entity types it applies to. It stops short of stating when not to use it or naming an alternative path, which keeps it at a 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources