Skip to main content
Glama
Sign In
killbottleneck-mcp

killbottleneck-mcp

Official
by tengolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

generate_image

Create illustrations, banners, headers, or posters from a detailed English prompt and get a public JPEG link. Choose square, banner, header, portrait, or landscape formats.

Instructions

Draw a picture (illustration, banner, header image, poster) with the instance's image model and return a public link to the JPEG. Write prompt in English as a detailed visual description and add "no text". Only when readable words must be in the picture, put the exact short text into text (only if the instance allows pictures with text; letters may come out wrong). format: square 1024×1024 (default), banner 1200×400, header 1536×640, portrait 512×896, landscape 1792×1024. Costs AI credits like an assistant message.

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": {
      "prompt": "<prompt>",
      "title": "<title>"
    },
    "name": "generate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
titleYesshort caption
formatNo
promptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does well on cost ('costs AI credits like an assistant message'), output form (public link to a JPEG), and the risk that rendered letters 'may come out wrong', but says nothing about failure modes, generation latency, or whether the resulting link is durable or editable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and return value are front-loaded in the first clause, followed by parameter guidance and cost, with no filler sentences. The format enumeration is dense but each entry contributes dimensions the enum alone does not convey.

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?

With no output schema and no annotations, the description still tells the agent what comes back (public JPEG link) and the cost of calling it, plus enough parameter guidance to construct a valid request. The remaining gap is the unelaborated `title` parameter and the absence of any error or limit information.

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 only 25%, so the description must compensate, and it largely does: `prompt` gets writing guidance (English, detailed visual description, append 'no text'), `text` gets a conditional use rule and a caveat about garbled letters, and `format` gets all five enum values with concrete pixel dimensions and a stated default. Only `title` is left to the schema's 'short caption'.

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?

States a specific verb and resource ('Draw a picture ... with the instance's image model') plus the concrete output ('return a public link to the JPEG') and enumerates the artifact types it covers (illustration, banner, header, poster). None of the sibling tools do image generation, so it is trivially distinguishable.

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?

Gives clear conditions for using the `text` parameter ('only if the instance allows pictures with text'), instructs writing prompts in English with 'no text' appended, and warns about credit cost. It stops short of explicit when-not-to-use guidance or naming an alternative tool for non-image tasks.

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