Skip to main content
Glama
STREONOR MCP

STREONOR MCP

by lde-medeiros

find_icons

Read-only

Search imported STREONOR icon packs to locate safe, self-contained SVG icons for scene and state previews, then render selected icons to PNG when needed.

Instructions

Search icon packs imported into STREONOR. Safe self-contained SVG icons can be rendered to PNG.

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": "find_icons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.2

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description does add one genuine behavioral trait beyond them: only "safe self-contained SVG icons" can be rendered to PNG, hinting that some results are not renderable. That constraint stays vague (what makes an icon 'safe self-contained' is undefined) and nothing is said about result ordering or volume.

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?

Two short sentences with no filler, and the core action is front-loaded. The second sentence is compact but sits awkwardly, since it is a rendering caveat rather than search semantics.

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?

An output schema exists, so return shape need not be explained, and annotations cover the safety profile. However, for a search tool with 0% schema description coverage, the definition omits matching semantics, the meaning of limit, and routing against resolve_icon/prepare_icon, leaving real gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters rely on the description, which mentions neither. It does not say what "query" matches against (name, tag, pack, file) or what "limit" (default 50) controls, so an agent must guess at matching behavior and result bounding.

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?

"Search icon packs imported into STREONOR" gives a specific verb (search) and resource (icons in local packs), which is clearly distinguishable from action/scene/profile siblings. The second sentence about PNG rendering is more of a caveat than a purpose statement, and the nearest neighbors (resolve_icon, prepare_icon) are not differentiated.

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?

Nothing states when to use this tool rather than resolve_icon or prepare_icon, and no prerequisites or exclusions are given. The line "Safe self-contained SVG icons can be rendered to PNG" implies a downstream use and a category of usable icons, but it is left implicit rather than spelled out as guidance.

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