Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

prepare_icon

Destructive

Create a square 1254×1254 PNG icon with optional solid background or edge-background replacement, saving to a new output path.

Instructions

Create a square 1254 PNG; output must not exist. Optional #RRGGBB background flattens transparency. replace_edge_background replaces the top-left connected background with tolerance 24. Does not edit a profile.

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": {
      "image_path": "<image_path>",
      "output_path": "<output_path>"
    },
    "name": "prepare_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
image_pathYes
output_pathYes
background_colorNo
replace_edge_backgroundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this as destructive and not read-only. The description adds useful behavior beyond annotations: the output must not already exist, background color flattens transparency, and edge background replacement uses tolerance 24. It does not discuss permissions or return values, but the core destructive behavior is clarified.

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 short and front-loaded, with the output requirement and key parameter behaviors stated efficiently. The fragment style is terse but readable, and no sentence is obviously wasteful.

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

Completeness3/5

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

For a four-parameter destructive image conversion tool with no output schema and no schema descriptions, the description covers output constraints, background behavior, and profile scope. It still leaves gaps around source image requirements, resizing/cropping behavior, and what successful output returns.

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 0%, so the description must carry parameter meaning. It usefully explains background_color as #RRGGBB and its flattening effect, and explains replace_edge_background with tolerance 24, plus the output_path existence constraint. It does not explain image_path semantics or accepted input formats.

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 specific action and output: create a square 1254 PNG. It adds a scope boundary with 'Does not edit a profile,' though it does not explicitly name sibling alternatives such as resolve_icon or prepare_boot_logo.

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

Usage Guidelines3/5

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

The description provides practical constraints such as 'output must not exist' and 'Does not edit a profile,' which imply when the tool is appropriate. However, it does not explicitly say when to use this instead of sibling tools like resolve_icon or prepare_boot_logo.

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