Skip to main content
Glama

search_by_mood

Find generative art algorithms by creative mood (e.g., cosmic, minimal, chaotic) and optionally refine results with style tokens.

Instructions

Search algorithms by creative mood or visual atmosphere.

Returns a dict with:
- mood (str): the normalized mood used for the query
- style (str | null): the style refinement if provided
- profile_summary (dict): the mood's associated categories and key concepts
- results (list): ranked manifest entries matching the mood

Each mood maps to a curated set of algorithm categories, concepts, and good_for
tags. The style parameter re-ranks results by matching its tokens against all
metadata fields. When the mood is unrecognized, returns an error dict containing
'error', 'available_moods', and a 'tip'.

Prefer search_algorithms for free-text queries without a clear aesthetic direction.
Use this tool when you have a specific visual mood in mind (e.g. 'cosmic',
'minimal', 'chaotic').

Available moods: ethereal, chaotic, geometric, organic, cosmic, minimal,
generative, retro, crystalline, topological, networked, geological.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moodYesCreative mood or visual atmosphere. Must be one of: ethereal, chaotic, geometric, organic, cosmic, minimal, generative, retro, crystalline, topological, networked, geological. Case-insensitive. Returns an error dict with available_moods when the value is not recognized.
styleNoOptional style refinement as free-text tokens (e.g. 'fluid', 'dark', 'crystalline', 'monochrome'). Tokens are matched against algorithm metadata to boost ranking within the mood results. Omit to use the mood profile alone.
limitNoMaximum number of results to return. Accepts integers in the range 1–50. Default: 8. Results are sorted by combined mood-profile and style score.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Describes return format (dict with mood, style, profile_summary, results), explains style re-ranking, and error handling. No annotations provided, so description carries full burden — and it clearly communicates all behavioral aspects of a read-only search tool.

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?

Compact yet comprehensive: one-sentence purpose, bullet-like return field listing, behavioral description, usage comparison, and explicit mood list. No redundant sentences; every line earns its place. Front-loaded with key purpose.

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?

Given three parameters (one required), no annotations, and presence of output schema (though not shown), the description covers all important aspects: return structure, parameter effects, error states, and sibling tool distinction. Highly complete for the tool's complexity.

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%, baseline 3. Description adds value beyond schema: explains style parameter re-ranking behavior ('matched against algorithm metadata to boost ranking'), and limit parameter sorting ('sorted by combined mood-profile and style score'). These non-trivial additions justify a 4.

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 clearly states the tool searches algorithms by creative mood, and explicitly distinguishes from sibling tool search_algorithms by specifying when to use each. It lists the exact 12 available moods, making the purpose highly specific and differentiated.

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?

Provides explicit guidance: use when you have a specific visual mood, prefer search_algorithms for free-text queries without clear aesthetic direction. Also documents error behavior for unrecognized moods and lists available moods, enabling correct agent decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asamiile/logic-lab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server