Skip to main content
Glama

Add a moodboard image set

inspo_add_images

Search Openverse for CC-licensed photos and illustrations, then add selected results to a moodboard as design references.

Instructions

Search CC-licensed photography/illustration on Openverse and add it to the board as moodboard references (art direction, photography style, textures).

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

Input Schema

NameRequiredDescriptionDefault
countNo
queryYes
sessionNoSession id. Defaults to the most recent session in this project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does disclose the external source (Openverse, CC-licensed) and the mutation (adds images to the board), which is real behavioral value. It omits what happens on no results, duplicate handling, whether login/auth is required (inspo_login exists as a sibling), and any rate-limit behavior from the external API.

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?

One front-loaded sentence with the action and source first and the purpose qualifier after; no filler, no repetition of the title.

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?

For a 3-parameter tool with no annotations and no output schema, the definition covers the what and where but leaves count behavior, default handling, and any sense of the result (added image count/ids) unaddressed. It is callable as written but an agent must probe to understand the side effects.

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 only 33%, with just 'session' documented in the schema. The description implies 'query' is the search term but says nothing about 'count' — its 1-16 range has no default documented — and does not explain how session scoping affects the target board beyond what the schema already states.

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?

States a specific verb pair (search + add) and resource (CC-licensed photography/illustration from Openverse added as moodboard references), with the intended content categories in parentheses. This clearly separates it from inspo_add_styles and inspo_add_component by content type, though no sibling is named explicitly.

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 use case (building moodboard/art-direction references) is implied by the parenthetical, which gives an agent a reasonable context to select it. There is no explicit when-not guidance, no mention of alternatives such as inspo_search or inspo_harvest, and no prerequisites stated.

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