Skip to main content
Glama
Sign In
sketchy-mcp

sketchy-mcp

by ddkbs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find a photo

find_image

Search freely licensed photos from Wikimedia Commons and Openverse to locate clear, frontal images of a single object for labeling in diagrams.

Instructions

Search freely licensed photos (Wikimedia Commons, Openverse; CC0, public domain, CC BY, CC BY-SA). Returns candidates with ids and thumbnails. Prefer clear, frontal photos of a single object.

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_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the photo should show, e.g. 'Arduino Uno board'
min_widthNoMinimum width in pixels (default 800)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.8

TDQS

A3.8/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose the meaningful traits: the licensed corpora searched (Wikimedia Commons, Openverse) and the license set (CC0/PD/CC BY/CC BY-SA), plus the shape of the return (candidates with ids and thumbnails). It omits result count, pagination, rate limits, and any failure behavior, so an agent still cannot predict the volume or cost of a call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what is searched and what comes back. Every clause carries information: sources, licenses, return shape, and query preference. No filler or restatement of the name.

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?

For a simple two-parameter read tool with no output schema, the description covers the essentials: corpus, licensing, and the fact that results are candidates with ids and thumbnails. It could be stronger by stating roughly how many candidates come back and that the ids feed downstream tools like download_model or open_link.

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 100%, so both `query` (with an example) and `min_width` (default 800, positive integer) are already documented. The description adds only indirect meaning through the 'clear, frontal, single object' phrasing hint, which supports query construction but says nothing about min_width or resolution trade-offs.

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?

The first sentence states a specific verb and resource (search freely licensed photos) and even names the corpora and license set. No sibling tool (search_parts, get_view, open_link) does image discovery, so the boundary is unambiguous from the name and text alone.

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?

"Prefer clear, frontal photos of a single object" is a useful query-shaping hint, but it is guidance on how to phrase a query, not when to pick this tool over an alternative. There is no mention of when-not to use it, or of how the returned ids relate to download_model/open_link.

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

Deploy Server

Other Tools