aetumi

Search Labs experiences by free text

find_experiences

Read-onlyIdempotent

Free-text search across ALL facets of the AETumi Labs reference experiences at once — industry, experience type, visual style and customer goal — returning the best ranked matches with name, industry, styles, goals, live url and industry hub url. AETumi Labs holds 31 live interactive reference experiences, published for study and reference; they are NOT catalog items for sale. Use this when the request COMBINES facets or uses wording that is not an exact facet value, for example dark cinematic automotive launch or glass beauty product reveal. If you already hold one exact industry, style or goal value and want the complete list for it, prefer filter_by_industry, filter_by_style or filter_by_goal, which are exhaustive rather than ranked. For commercial assets to license and ship, use search_3d_web_assets. Read-only, no authentication, no side effects; returns public metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many experiences to return, 1-12, default 5.
`query`	Yes	Free text describing the experience wanted; may mix industry, visual style, customer goal and experience type, e.g. dark cinematic automotive launch.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	Number of matching AETumi Labs experiences.
`results`	No	Matching experiences with slug, name, industry, visualStyles, customerGoals and live url.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 28, 2026

changedInput schema / properties / limit / description

Previous value: -"1-12, default 5"New value: +"How many experiences to return, 1-12, default 5."

changedInput schema / properties / query / description

Previous value: -"Free text describing the experience you want."New value: +"Free text describing the experience wanted; may mix industry, visual style, customer goal and experience type, e.g. dark cinematic automotive launch."

Changed1 schema field changedSep 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "Number of matching AETumi Labs experiences.",
+      "type": "integer"
+    },
+    "results": {
+      "description": "Matching experiences with slug, name, industry, visualStyles, customerGoals and live url.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description adds real context beyond that: ranked (not exhaustive) results, the size of the corpus (31 live reference experiences), and the important caveat that these are study references and NOT catalog items for sale. It does not discuss pagination or ranking algorithm, which keeps it short of a 5.

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-loads the core action and scope, then routes to siblings, then qualifies the dataset. Every sentence carries information, though the enumeration of return fields (name, industry, styles, goals, urls) is somewhat listing-heavy for a tool that has an output schema.

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?

An output schema exists, so return values need no elaboration, and the description still covers scope, ranking behavior, dataset nature, auth/no-side-effects, and sibling routing. An agent has everything needed to call this correctly.

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 parameters are already documented, including the limit range and default and the query's mixable facets. The description's example ('dark cinematic automotive launch') largely restates the schema's own example, so it adds little beyond the baseline.

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?

States a specific verb and resource (free-text search across the AETumi Labs reference experiences) and names the exact facets searched. It explicitly distinguishes itself from filter_by_industry/filter_by_style/filter_by_goal and search_3d_web_assets, so an agent can route correctly without opening any schema.

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 an explicit when-to-use condition (requests that COMBINE facets or use non-exact wording, with concrete examples) and explicit alternatives with the condition that selects them (exact facet value → use the exhaustive filter_* tools; commercial assets → search_3d_web_assets). Nothing is left to inference.

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

All aetumi 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.