Skip to main content
Glama

artwork_make_it_cooler

Apply targeted, AI-suggested improvements to GIMP artwork by converting model suggestions into safe semantic edits.

Instructions

Ask the selected model for a few targeted improvements and execute them through safe semantic GIMP actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
presetNoMake it cooler

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions 'safe semantic GIMP actions', suggesting non-destructive or guarded execution, but does not state required permissions, reversibility, side effects, or what happens to the existing artwork. This is insufficient for a mutation-style tool.

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 description is a single, front-loaded sentence with no filler. It is efficiently sized, though it could be slightly more structured by specifying the model selection and GIMP action scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that orchestrates AI-driven improvements, likely with side effects, the description is thin. It omits parameter meaning, prerequisites, and execution flow. Although an output schema exists, the description still leaves critical context about model selection and safe action boundaries unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention either parameter (job_id, preset). It does not explain what a job_id refers to, what preset defaults or alternatives exist, or how the model is selected. It fails to compensate for the complete lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear two-step purpose: ask the selected model for improvements, then execute them through GIMP actions. It conveys the tool is an AI-assisted enhancement operation, but it does not differentiate itself from the many other GIMP/artwork siblings (e.g., artwork_job_run, filter_apply) that could also modify artwork.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives like artwork_job_run, followup, or manual filter operations. The only implied context is that it is for making artwork 'cooler', but no when/not conditions or prerequisites are given.

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