Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List skills

list_skills
Read-only

Browse available multi-step workflow instructions and creative recipes—covering ad research, ad planning/rendering, product photoshoots, and raw generation—to identify and load the right skill bundle for your marketing task.

Instructions

List the bundled Hermoso SKILLS — multi-step workflow instructions (SKILL.md) that orchestrate the other tools (research an ad space, plan+render a finished ad, product photoshoot, raw generation) — plus the in-app strategy skills and creative recipes. Call get_skill to load a bundle. Read-only, free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "bundles": {
-      "description": "bundled skills ({name, description}) loadable via get_skill",
-      "items": {},
-      "type": "array"
-    },
-    "inApp": {
-      "description": "in-app strategy skills + creative recipes ({id, kind/group})",
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description largely repeats that with 'Read-only'. It adds useful extras like 'free' and specifies the scope (bundled plus in-app strategy skills and creative recipes), but it does not disclose return format, ordering, or whether the listing is exhaustive. The read-only behavior is covered by annotations, so the description adds modest value beyond them.

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?

The description is a single compact passage with the core action front-loaded. Every clause adds value: what skills are, examples, scope, routing to get_skill, and cost/safety. There is no filler or redundant restatement.

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?

For a zero-parameter, list-style tool with strong safety annotations, the description is complete. It explains what the tool returns conceptually, gives the domain context needed to interpret the list, names the related loading tool, and notes cost. No output schema exists, but the return value of a skill listing is obvious from the description.

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?

The tool has zero parameters and schema description coverage is 100%, so there is no parameter meaning for the description to clarify. Baseline 4 applies for parameterless tools; the description appropriately spends no space on parameters.

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 states a specific verb ('List') and resource ('bundled Hermoso SKILLS'), then defines what a skill is with concrete examples ('research an ad space, plan+render a finished ad'). It also distinguishes itself from related tools by naming get_skill, which prevents confusion with load/delete/save skill operations.

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?

The description explicitly tells the agent to 'Call get_skill to load a bundle', making the boundary between listing and loading clear. It frames the tool's purpose as discovery/orientation, and the added 'Read-only, free' note reinforces when this is a safe, low-cost choice.

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