Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Search everything the brand has

search_brand_library
Read-onlyIdempotent

ONE search over everything a brand already has, to reuse it before making anything new: films (by title), generated images (by prompt), the SCENES of its films (what is seen, words on screen, the voice line — "oven" finds the scene that showed the oven) and the brand Library (owner uploads, logos, product shots, videos: by name, description and what the picture shows). Every word must match, in any order. Optional kinds narrows to video (films), image, clip (film scenes), upload, brand_asset. Returns one list, title matches first then newest, each item with a creation_ref and the ids tools take: project_id (a film; for a scene, the film it is in, plus scene_id / scene_number, clip_id and the clip's url once made), asset_id (a brand Library file: it goes wherever a Library id is taken — a post's media, a film's own media, picture references, video_asset_id), library_id (a creation, as list_creations returns it). Free, read-only.

Input Schema

NameRequiredDescriptionDefault
kindsNoOnly these: video (films), image (generated images and logos), clip (film scenes), upload (owner uploads), brand_asset (other brand Library files)
limitNo
queryYesA few words for what to find, e.g. "oven" or "logo"
brand_idYesBrand workspace id from list_brands
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses matching semantics ("Every word must match, in any order"), result ordering (title matches first, then newest), the exact return shape with creation_ref and each id, and where each id is accepted downstream. That is substantive context an agent cannot get from the annotations.

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-loaded with the core purpose, then progressively details sources, matching rules and return fields. It is a single dense run-on sentence chain with some heavy parenthetical nesting, but virtually every clause carries information an agent needs.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, explaining the list, ordering and id semantics. Minor gap: limit's default and any result-count/pagination behavior are left unspecified.

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 80%, so baseline is 3; the description adds real meaning by explaining that query terms are AND-matched in any order and by mapping kinds values to concrete content types (video=films, clip=film scenes, brand_asset=other Library files). limit and its default behavior are not addressed.

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 scope: one search across films, generated images, film scenes and brand Library files, with a clear 'reuse before making new' framing. It is immediately distinguishable from list_brand_assets, list_creations and find_creation, which are narrower or id-based.

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?

"to reuse it before making anything new" gives a clear when-to-use context, and the parenthetical examples ("oven" finds the scene that showed the oven) make the matching intent concrete. It does not explicitly name the alternatives (list_brand_assets, find_creation) or state when NOT to use it, which keeps it from a 5.

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

All Mondovo toolsInspect
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