Skip to main content
Glama
Sign In
Shared Skills Registry MCP

Shared Skills Registry MCP

by cobibean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

install_shared_skill

Installs a named shared skill from the registry into your local skills directory, with options for category and overwrite settings.

Instructions

Install a shared skill into a configured local skills directory.

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": "install_shared_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
overwriteNo
skills_rootNo
target_categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as side effects (e.g., overwriting existing files), permissions required, or error conditions. The minimal description fails to compensate for the lack of annotations.

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 very concise (one sentence) and front-loaded with the main action. However, it sacrifices valuable details that could be added without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters (1 required), no output schema, and no annotations, the description is insufficient. It lacks context about where the skill comes from, what installation entails, and any constraints, making it hard for an agent to use correctly.

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

Parameters1/5

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

The description adds no meaning to the parameters. With 0% schema description coverage, the agent must rely on parameter names alone, which are insufficient for understanding purpose (e.g., 'skills_root', 'target_category').

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 clearly states the action (install), the resource (shared skill), and the destination (local skills directory). It effectively differentiates from sibling tools which focus on describing, listing, retrieving, and searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidelines are provided. The description does not specify when to use this tool versus alternatives, nor does it mention any prerequisites or conditions for installation.

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