Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List saved elements

list_elements
Read-onlyIdempotent

List saved @name elements—people, places, or products—to reference them in image, video, or ad prompts. Filter by kind to find the right saved asset.

Instructions

Saved people, places and products, each with an @name. FREE. An @name in an image or video prompt or an ad brief ("@Sarah in @Kitchen") uses that saved picture as the reference.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_elements"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoonly this kind

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.532

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context — that elements are FREE and are consumed as @name references in prompts — but says nothing about return shape, pagination, or limits.

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?

Two short sentences, front-loaded with the resource definition. 'FREE' is a one-word interjection that carries cost information for the agent, though it reads slightly like marketing copy rather than definition.

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 simple, annotation-rich, single-optional-param read tool with no output schema, an agent has enough to invoke it correctly. What is missing is any indication of what the listing returns (names only? names plus images?), which the description only partially covers via 'each with an @name'.

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% and the single optional 'kind' parameter has an enum, so the filter is fully documented structurally. The description never mentions the kind filter and adds no meaning beyond the schema; baseline 3 applies.

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?

The description defines the resource precisely — saved people, places and products, each with an @name — which clearly separates 'elements' from siblings like list_creators, list_brands or list_product_photos. The listing action itself is only implied by the name/title rather than stated as a verb in the description, which keeps it from a 5.

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?

There is no explicit when-to-use/when-not-to-use guidance or named alternative. However, the sentence about @name references in image/video prompts and ad briefs implies the reason to call this: to discover usable @names for later prompts. Usage is implied rather than directed.

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

Deploy Server

Other Tools