Skip to main content
Glama
Sign In
Hermoso

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get skill

get_skill
Read-onlyIdempotent

Load a bundled skill’s full SKILL.md workflow instructions by name or a built-in in-app skill by ID, then follow them to run the workflow with Hermoso’s other tools.

Instructions

Load a bundled skill’s full SKILL.md workflow instructions by name (from list_skills), or a built-in in-app skill by its id (e.g. youtube_script, retention_skeleton). Follow the loaded instructions to run that workflow with the other tools. Read-only, free.

Input Schema

NameRequiredDescriptionDefault
nameYesbundle name from list_skills, e.g. hermoso-generate

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": {
-    "name": {
-      "description": "the loaded skill bundle name",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. Addedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world behavior. The description adds value beyond them by stating 'free' (billing context) and explaining what the loaded content is and what to do with it (follow instructions to run the workflow), which is genuinely useful next-step guidance.

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 action and kept to a couple of sentences. Minor redundancy: 'Read-only' restates readOnlyHint, though 'free' adds new billing information, so the trailing phrase mostly earns its place.

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?

For a single-parameter, non-destructive tool with no output schema, the description explains what is loaded, where the valid name comes from, and what to do with the result. It does not describe error behavior for an invalid name, but otherwise it is complete.

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%, but the schema only calls the param a 'bundle name from list_skills,' whereas the description reveals the param can also be a built-in in-app skill id and gives examples (youtube_script, retention_skeleton). This adds real meaning beyond the schema.

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?

Specific verb+resource: 'Load a bundled skill's full SKILL.md workflow instructions.' It clearly distinguishes the resource (a skill's instructions) from siblings like list_skills, save_skill, and delete_skill, and explains both the bundled-name and built-in-id forms.

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?

It routes the agent to list_skills for obtaining a valid name and says to follow the loaded instructions to run the workflow with other tools. It gives clear context but does not name an explicit 'use X instead' alternative or when-not case.

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