Skip to main content
Glama
Sign In

Youform

by io.github.mkmaker
OverviewDiscussionsAdmin

Search icons

search-icons-tool
Read-only

Search Youform's hosted icon and illustration library by subject, people, activity or style. Returns 12 results per page, descriptive keywords, full image URLs, thumbnails and available style ids. Empty style-filtered searches include other-style alternatives when available; offer these only if a style change is acceptable. empty_reason=no_match means no match for this query in any style. Use the full url with update-block-tool: options[].image_url for radio/checkbox/ranking, or cover_image_url for a block cover. Search does not edit or publish a form. Omit query to browse; reuse a style id for consistent artwork.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search-icons-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Each page contains at most 12 icons.
queryNoOne subject per search; all words must match, e.g. coffee, girl with glasses, doctor. Omit to browse.
styleNoOptional exact style id returned by a previous search, e.g. 3d-realistic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read operation, and the description adds real behavioral context: 12 results per page, what each result contains (keywords, full URLs, thumbnails, style ids), and the semantics of empty style-filtered results including empty_reason=no_match. It also rules out side effects ("does not edit or publish a form").

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?

Front-loaded with purpose and return shape before edge cases and integration advice, with no filler sentences. It runs long and packs several ideas into semicolon-joined clauses, which slightly reduces scannability but each clause carries distinct information.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing returns and does so thoroughly (page size, fields, thumbnail vs full URL, style ids). For a 3-parameter, zero-required search tool, an agent has everything needed to call it and handle empty results.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds useful meaning: omitting query browses the whole library rather than erroring, and reusing a style id yields consistent artwork across picks. The "one subject per search" constraint largely restates the schema's example text.

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

Purpose5/5

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

Opens with a specific verb and resource: "Search Youform's hosted icon and illustration library by subject, people, activity or style." This clearly distinguishes it from siblings that mutate forms or blocks, and explicitly states "Search does not edit or publish a form."

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

Usage Guidelines5/5

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

Gives concrete when-to-use guidance: "Omit query to browse; reuse a style id for consistent artwork," plus how to consume results ("Use the full url with update-block-tool: options[].image_url ... or cover_image_url"). It also covers a conditional case, advising that cross-style alternatives be offered "only if a style change is acceptable."

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

All Youform toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources