tattoo-brief-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_tattoo_briefC | Turn a tattoo idea, style, placement and size into a structured brief to bring to a tattoo artist. |
| check_small_size_legibilityB | Heuristic blur-risk check for tattoo details at a given size. Rules of thumb only, not a guarantee. |
| line_art_promptC | Write a clean line-art prompt (plus negative prompt) for an AI tattoo generator. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
line_art_prompt and build_tattoo_brief both take a tattoo idea and return text, so an agent could momentarily hesitate over which produces the AI prompt versus the human-facing brief. Their descriptions do clarify the distinction (generator prompt + negative prompt vs. structured artist brief), and check_small_size_legibility is clearly separate.
All three names use snake_case, and two follow a verb_noun/verb_phrase pattern (build_tattoo_brief, check_small_size_legibility). line_art_prompt is a noun phrase rather than a verb-led name, a minor deviation from an otherwise consistent convention.
Three focused tools fit a narrow, well-defined pipeline (idea → brief → prompt → legibility check) with no filler. It sits at the thin end of the suggested range, but each tool has a distinct role, so it is not under-scoped.
The surface covers generating a prompt, building a brief, and a size-legibility heuristic, but there is no way to refine or update an existing brief/prompt after feedback, and no style or placement reference lookup. Agents can work around this by re-calling tools from scratch, but iteration is a real gap.