Skip to main content
Glama

emdly

by com.emdly

Install Skill

install_skill

Install a skill into the agent you are running in. Returns the complete skill file and the exact path to write it to — YOU must then create that file verbatim (Claude Code: .claude/skills//SKILL.md, so it becomes available as /; other agents: ./skills/.md) and tell the user where it is. Counts the install. Use target=hermes for Hermes Agent, target=generic for any other agent, scope=user to install for all Claude Code projects. When emdly agent hosting is enabled and you have a hosted agent, pass agent= to install there instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoHosted agent name (only when emdly agent hosting is enabled and you have one).
scopeNoClaude Code only: project (default, .claude/skills in the current project) or user (~/.claude/skills, every project).
skillYesowner/name, e.g. opsmith/jira-ticket-scorer
targetNoWhere the file goes: claude-code (default) → .claude/skills/<name>/SKILL.md; hermes → ~/.hermes/skills/<category>/<name>/SKILL.md; generic → ./skills/<name>.md.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With empty annotations, the description carries the full burden, and it discloses a crucial non-obvious behavior: the tool does not write the file itself — 'YOU must then create that file verbatim.' It also reveals the side effect 'Counts the install' and specifies exact installation paths per target, which is more than most definitions provide.

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 description is dense but not bloated; every sentence contributes critical information. The core purpose is front-loaded, followed by the return contract and parameter routing. It is longer than average, but the complexity of the tool (multiple targets, follow-up write action) justifies the length.

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?

There is no output schema, so the description correctly explains return values (complete skill file and path) and the required post-call action. It covers all parameter scenarios and paths. Minor omissions like overwrite behavior, error cases, and more detail on 'Counts the install' prevent a 5.

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%, so the baseline is 3. The description adds value by prescribing parameter choices for real-world scenarios: target=hermes, target=generic, scope=user for all projects, and agent= for hosted agents. This goes beyond the schema's field descriptions and helps the agent choose correct values.

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 opens with a specific verb and resource: 'Install a skill into the agent you are running in.' It goes on to describe the return contract (complete skill file and exact path) and the agent's required follow-up, which clearly distinguishes this from sibling tools like get_skill, search_skills, and submit_skill.

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?

The description provides explicit selection guidance for target ('Use target=hermes for Hermes Agent, target=generic for any other agent'), scope ('scope=user to install for all Claude Code projects'), and agent ('pass agent= to install there instead'). It does not explicitly contrast with alternative tools, but the parameter routing rules are concrete and actionable.

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

All emdly toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: brain_get/brain_list/brain_search/brain_write cover memory operations, while get_collection/get_skill/install_skill/search_skills/submit_skill handle skill discovery, retrieval, installation, and submission. No two tools overlap in function; even the search vs get pairs are distinct.

Naming Consistency3/5

The brain_* prefix provides a consistent pattern for memory tools, but the skill tools use mixed conventions: get_collection, get_skill, install_skill, search_skills, submit_skill — no shared prefix or uniform verb_noun structure. This inconsistency is noticeable but each name is still readable.

Tool Count5/5

With 9 tools covering two domains (memory and skills), the count is well-scoped. Each tool earns its place, and the number is within the ideal range for a focused server.

Completeness4/5

The brain tools cover list, get, search, and write, but lack an explicit delete operation. The skill tools cover search, get, install, submit, and collection listing, but no uninstall. These are minor gaps that agents can work around; the core workflows are complete.

Resources