Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

resolve_icon

Prepares a matching 1254 PNG icon from an explicit image or exact installed match, otherwise generates a black label icon; returns path, origin, and hash for set_icon with no network requests.

Instructions

Prepare a matching 1254 PNG. Prefer an explicit image, then an exact installed icon match, otherwise generate a black label icon. No network requests. Return path, origin and hash for set_icon.

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": {
      "query": "<query>"
    },
    "name": "resolve_icon"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
image_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description adds genuinely new context: no network requests are made, a deterministic fallback icon is generated when nothing matches, and the result includes path, origin and hash. What it omits is whether the generated PNG is written to disk and what happens when the query matches nothing at all.

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, front-loaded with the action and followed by the policy and output contract; nothing is redundant. The unexplained '1254' token and the compressed phrasing cost it a point.

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

Completeness4/5

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

With two parameters, no output schema and no nested objects, the description covers the essentials: resolution strategy, side-effect profile (no network), and the return fields. It stops short of error behavior and whether the produced PNG persists, which matters for a non-read-only tool.

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% for both parameters, so the description must carry the load. The precedence ordering does clarify the relationship between image_path ('an explicit image') and query (the 'exact installed icon match'), but it never says what form a query takes or whether supplying image_path bypasses lookup entirely.

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 definition states a concrete verb and artifact: 'Prepare a matching 1254 PNG' with a defined resolution order and output. That is far more specific than the bare name, though it never distinguishes this from the sibling prepare_icon or find_icons, so an agent must guess which resolver to call.

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 precedence chain (explicit image, then exact installed icon match, then generated black label) tells the agent how resolution behaves, and 'for set_icon' implies this is a preparatory step. There is no explicit when-to-use versus prepare_icon or find_icons, and no statement of when this tool should be avoided.

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