Skip to main content
Glama

mcp_install

Registers a child MCP with global, per-project, or per-file routing so agents can run isolated tool instances using templated paths and environment settings.

Instructions

安装(注册)一个子 MCP。strategy 可选 global / per_project / per_file;args/env/cwd 支持 ${PROJECT_ROOT} ${DB_PATH} 等模板。

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>",
      "command": "<command>"
    },
    "name": "mcp_install"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNo
envNo
argsNo
nameYes
commandYes
db_fileNo
requiredNo
strategyNoper_project
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutating registration tool. It discloses the strategy dimension and template substitution but says nothing about persistence, overwrite/idempotency on re-install, whether the new server becomes active immediately or needs mcp_restart, or any permission requirements.

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?

Two compact sentences, no filler, with the core action front-loaded and parameter hints packed into the second clause. The dense parenthetical/semicolon style is efficient though slightly terse for non-Chinese readers mixing in parameter names.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the strategy/template hints are valuable. But for a 9-parameter mutation tool with no annotations and 0% schema coverage, key inputs (command, db_file, required) and post-install behavior are left undocumented, leaving the agent to guess.

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% across 9 parameters, so the description must compensate and does so partially: it enumerates the three strategy values (global/per_project/per_file) — real value since the schema has no enum — and explains that args/env/cwd accept ${PROJECT_ROOT}/${DB_PATH}-style templates. However, name, command, db_file, required, and description parameters remain entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb plus resource: "安装(注册)一个子 MCP" (install/register a child MCP), which an agent can readily distinguish from list/get/remove/update siblings by verb alone. It stops short of naming an alternative or contrasting with mcp_update, so it is clear but not sibling-differentiating.

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

Usage Guidelines3/5

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

"Install (register)" implies this is the creation path and implicitly the opposite of mcp_remove/mcp_update, but the description never states when to use this versus mcp_update or what happens if the name already exists. Usage is inferable from the verb only, with no exclusions or alternatives given.

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