Skip to main content
Glama
JeremyLakeyJr

Friday MCP Server

install_skill_from_url

Download, validate, install, and optionally activate a markdown-based skill from a URL to extend the MCP server's capabilities.

Instructions

Download, validate, install, and optionally activate a skill from a URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
activateNo

Implementation Reference

  • The MCP tool handler for 'install_skill_from_url'. It downloads skill markdown from a URL via httpx, then delegates to skill_store.install_skill_from_markdown for validation, installation, and optional activation.
    @mcp.tool()
    async def install_skill_from_url(url: str, activate: bool = True) -> dict:
        """Download, validate, install, and optionally activate a skill from a URL."""
        async with httpx.AsyncClient(follow_redirects=True, timeout=15.0) as client:
            response = await client.get(url)
            response.raise_for_status()
        return skill_store.install_skill_from_markdown(
            response.text,
            source=url,
            source_type="url",
            activate=activate,
        )
  • Input schema for the tool: 'url: str' (required) and 'activate: bool = True' (optional, defaults to True).
    @mcp.tool()
    async def install_skill_from_url(url: str, activate: bool = True) -> dict:
        """Download, validate, install, and optionally activate a skill from a URL."""
        async with httpx.AsyncClient(follow_redirects=True, timeout=15.0) as client:
            response = await client.get(url)
            response.raise_for_status()
        return skill_store.install_skill_from_markdown(
            response.text,
            source=url,
            source_type="url",
            activate=activate,
        )
  • Registration of the 'install_skill_from_url' tool via the @mcp.tool() decorator inside the register() function. The register() function is called from tools/__init__.py's register_all_tools.
    def register(mcp, *, skill_store) -> None:
        @mcp.tool()
  • Core helper SkillStore.install_skill_from_markdown() called by the handler. Parses, validates, backs up existing skill if present, writes the skill file, and updates the registry.
    def install_skill_from_markdown(
        self,
        markdown: str,
        *,
        source: str,
        source_type: str,
        activate: bool = True,
    ) -> dict[str, Any]:
        document = self._parse_skill(markdown)
        self._ensure_compatible(document.min_server_version)
    
        registry = self._load_registry()
        target_path = self.installed_dir / f"{document.skill_id}.md"
        backup_path = None
    
        if target_path.exists():
            timestamp = self._timestamp_slug()
            backup_path = self.backups_dir / f"{document.skill_id}-{timestamp}.md"
            shutil.copy2(target_path, backup_path)
    
        target_path.write_text(self._serialize_skill(document), encoding="utf-8")
    
        record = {
            "id": document.skill_id,
            "name": document.name,
            "version": document.version,
            "description": document.description,
            "capabilities": document.capabilities,
            "min_server_version": document.min_server_version,
            "active": activate,
            "source": source,
            "source_type": source_type,
            "installed_at": self._timestamp(),
            "checksum": self._checksum(target_path.read_text(encoding="utf-8")),
            "path": str(target_path),
            "backup_path": str(backup_path) if backup_path else None,
        }
        registry[document.skill_id] = record
        self._save_registry(registry)
        return record
  • Tool registration orchestrator that calls skills.register(mcp, skill_store=skill_store) to register all skill tools including install_skill_from_url.
    def register_all_tools(mcp, *, config, skill_store) -> None:
        system.register(mcp, config=config)
        utils.register(mcp)
        web.register(mcp, config=config)
        workspace.register(mcp, config=config)
        skills.register(mcp, skill_store=skill_store)
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It names the steps but omits critical details like error handling on invalid URL, permission requirements, or whether it overwrites existing skills.

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?

Single sentence front-loading all key actions with no redundancy. Every word adds value.

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 no output schema and moderate complexity, description lacks details on return values, validation outcomes, and post-installation state. Insufficient for reliable tool selection.

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

Parameters3/5

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

Schema description coverage is 0%, so description carries full burden. It explains the 'url' parameter as the source and mentions optional 'activate' but fails to note the default value of true or any constraints on the URL format.

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 verb 'install' and resource 'skill', and specifies the source 'from a URL'. It distinguishes from sibling tool 'install_skill_from_markdown' which uses a different source format.

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 guidance on when to use this tool versus alternatives like 'install_skill_from_markdown' or on prerequisites. The 'optionally activate' is mentioned but lacks context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JeremyLakeyJr/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server