Skip to main content
Glama

Tattoo Design Generator - Abracadabrax

Prepare Tattoo Design

prepare_tattoo_design

Prepare an original tattoo design with Abracadabrax from an idea, a style (blackwork, fine line, traditional, neo-traditional, watercolor, geometric, Japanese), the ink and the body placement, as one stencil-ready design or a flash sheet. Returns the settings and the credits required; nothing is generated and no credits are spent. No sign-in is needed to prepare. Original designs only: do not use it for copyrighted characters, existing franchises, brand logos, trademarks or real celebrities; offer the user an original alternative instead. Text only: do not use it for uploaded, attached or reference images or videos (editing, background removal, upscaling, image-to-video); for those, point the user to the Abracadabrax workspace.

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": {
      "idea": "<idea>"
    },
    "name": "prepare_tattoo_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
inkNoblack-and-gray (default), black-only or color.
ideaYesWhat the tattoo shows, e.g. a wolf howling at a crescent moon framed by pine trees.
styleNoTattoo style, e.g. fine line, blackwork, American traditional, neo-traditional, watercolor, geometric, Japanese.
layoutNostencil (default, one design) or flash-sheet (several small designs).
model_idNoOptional image model id: nano-banana-pro (default), flux-2-pro, nano-banana-2.
placementNoWhere it goes on the body, e.g. forearm, shoulder, ankle; shapes the proportions.

Output Schema

NameRequiredDescriptionDefault
jobNo
stateYes
balanceNo
messageYes
projectYes
dashboard_urlYes
credits_requiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, idempotentHint=false and destructiveHint=false, which on their own could read as a mutating tool. The description resolves the ambiguity by clarifying that nothing is generated and no credits are spent, that it returns settings plus credit cost, and that no sign-in is required — context the annotations cannot convey.

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?

Front-loads purpose then behavior then exclusions in a tight sequence. No filler; every sentence (costs nothing, sign-in not needed, copyright limits, image workflow redirect) carries decision-relevant information.

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 a six-parameter schema with an output schema, the description does not need to explain return values but still identifies what is returned (settings and credits) and covers the safety and scoping policies an agent needs. Nothing material for correct invocation is missing.

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 schema already documents all six parameters including enums and defaults. The description restates the key inputs (idea, style, ink, placement, layout) and enumerates style values, but adds little syntax or format meaning beyond what the schema provides, so the baseline 3 applies.

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 (prepare) and resource (tattoo design) with the named provider Abracadabrax, and distinguishes itself from the sibling generate_media by explaining that it only prepares settings and costs nothing. An agent can tell exactly what this does 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit about when to use it (from an idea, style, ink and placement, as stencil or flash sheet) and when not to: copyrighted characters, franchises, logos, trademarks and celebrities, plus all image/video workflows, each with a named redirect (offer original alternative; use the Abracadabrax workspace). Both exclusions and alternatives are spelled out.

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