Skip to main content
Glama
Sign In

Emero

by io.github.EmeroAI
OverviewDiscussionsAdmin

Load skill

load_skill
Read-onlyIdempotent

Load emero's guidance for a task before your first use of it (skill v162). Skills are cached per version: if the steps of a skill you loaded earlier are no longer visible in this chat (e.g. only a summary of it remains), load it again. Start every generation with load_skill("generate") (the step-by-step procedure and the tag generate requires); craft skills for its Step 7: make-image, make-video, make-music, make-speech, upscale-video. Also: art-direction, combining-videos, organizing-generations. Call load_skill("index") to list every available skill + workflow. (Name is a free string so new skills/workflows can appear without reconnecting.)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely behavioral context beyond that: skills are cached per version, and a reload is required when only a summary of the skill remains in the chat — a non-obvious stateful trait. It stops short of describing error behavior for unknown names or the exact shape of the returned 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?

The critical instruction (load before first use, and the "generate" starting point) is front-loaded, and every sentence carries information. A few parenthetical asides make it denser than necessary, but nothing is redundant filler.

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 single-parameter loader with a simple schema and no output schema, the definition covers the required trigger, the cache/reload rule, the enumerated skill catalog, and a discovery path. There is little an agent would need to know before calling it that is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema only says 'name: string, minLength 1', so the description carries the entire burden — and it does, by giving concrete valid values ("generate", "index", make-image, make-video, make-music, make-speech, upscale-video, art-direction, combining-videos, organizing-generations) and explaining why the name is a free string rather than an enum.

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 first sentence gives a specific verb and resource — 'Load emero's guidance for a task' — and the body enumerates the exact skill names available (generate, make-image, make-video, art-direction, combining-videos, etc.), making it unmistakably distinct from siblings like 'generate' or 'view'.

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?

Explicit when-to-use rules: load before first use of a skill, always start a generation with load_skill("generate"), and reload if the previously loaded steps are no longer visible because of versioned caching. It also names the alternative path, load_skill("index"), for discovery.

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

All Emero 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