Crypto, web, finance and app data tools

Free Image Search

free_image_search

Search openly licensed images (Creative Commons and public domain) from Flickr, Wikimedia and museums via Openverse: image URL, size, creator, license and a ready-made attribution line. Filter to commercially usable images. Use to illustrate posts, slides or sites legally.

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": {
      "q": "<q>"
    },
    "name": "free_image_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes
`limit`	No
`license_type`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses licensing scope, commercial-use filtering, and attribution output, but it omits read-only/search semantics, rate limits, pagination, or result behavior. For a simple search tool this is adequate but not rich.

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?

Two tightly written sentences with no filler. Source and return-value details are front-loaded, followed by the practical usage guidance.

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?

The tool is simple, has only three parameters, and has an output schema, which reduces the description's burden. Still, parameter semantics are undocumented and pagination/limit behavior is unaddressed, leaving meaningful gaps for correct invocation.

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 the description must compensate for undocumented parameters. It hints at the license_type concept via 'commercially usable images' but does not explain q, limit, or how license filtering maps to the license_type parameter.

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 description states a specific verb and resource: searching openly licensed images via Openverse, including Flickr, Wikimedia, and museums. It also names the returned fields (image URL, size, creator, license, attribution), making the tool clearly distinguishable from non-image-search siblings.

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

Usage Guidelines4/5

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

It gives clear usage context: 'Use to illustrate posts, slides or sites legally' and notes the commercial-use filter. However, it does not explicitly name when not to use it or identify any alternative image-search tool, which is understandable given the sibling list lacks a direct competitor.

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

All Crypto, web, finance and app data tools tools Inspect

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

Need Help?