Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

prepare_boot_logo

Destructive

Prepare a PNG boot logo for a STREONOR device menu by cropping to fill or padding with black, while leaving the device unchanged.

Instructions

Prepare a PNG for STREONOR's Devices menu. Cover crops to fill. Contain preserves the whole image with black padding. The device is unchanged.

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

Input Schema

NameRequiredDescriptionDefault
fitNocover
device_idYes
image_pathYes
output_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false; the description adds that the device itself is not modified, which usefully scopes the effect to files. It does not say whether output_path is overwritten or what happens if image_path is missing, so the destructive behavior is only partially characterized. 'The device is unchanged' is not a direct contradiction of destructiveHint since it describes device state, not file writes.

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?

Four short sentences with the purpose front-loaded and no filler. The final sentence ('The device is unchanged') is terse to the point of ambiguity about what exactly remains unchanged, but nothing is wasted.

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?

This is a destructive, file-writing tool with three required parameters, no output schema, and zero schema documentation, yet the description says nothing about output overwrite behavior, path expectations, or device_id semantics beyond the reassurance about the device. For a mutation tool with this much structured-data silence, the coverage is thin.

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 does explain the two fit behaviors (cover crops to fill, contain pads with black) even though it never names the 'fit' parameter. The device_id, image_path, and output_path parameters receive no treatment at all, relying purely on self-descriptive names.

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?

States a specific verb and resource — preparing a PNG for STREONOR's Devices menu — so the agent knows the artifact produced. It does not differentiate itself from the sibling prepare_icon, which sounds like a near-identical image-preparation task, leaving selection ambiguity.

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 'Devices menu' phrasing implies the context in which this tool applies, and the cover/contain explanation implies when each fit is appropriate. However, there is no explicit when-to-use/when-not guidance and no mention of prepare_icon as the alternative for other image types.

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