Skip to main content
Glama
Sign In
publish-pilot-mcp

publish-pilot-mcp

by acus9345
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

verify_install

Installs a published package or clones a repo in a clean temp folder, then runs commands in order and stops at the first failure to confirm installation and executables work.

Instructions

In a fresh temp folder, install the published package (or clone repoUrl) and run commands in order, stopping at the first failure. Its executables are on PATH.

Input Schema

NameRequiredDescriptionDefault
nameNo
commandYesList of commands (PowerShell on Windows, sh elsewhere)
repoUrlNo
versionNo
registryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / command / description
      Previous value: -"Commands to run in the folder (PowerShell on Windows, sh elsewhere). Prefer a list: each one must succeed before the next runs."New value: +"List of commands (PowerShell on Windows, sh elsewhere)"
    • removedInput schema / properties / registry / description
      Removed value: -"Package registry: npm, pypi (PyPI) or crates (crates.io)."
    • removedInput schema / properties / repoUrl / description
      Removed value: -"https://github.com/owner/repo — clone instead of installing."
  2. Changed3 schema fields changedv0.3.0
    • addedInput schema / properties / command / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  }
+]
    • changedInput schema / properties / command / description
      Previous value: -"Command to run in the folder (PowerShell on Windows, sh elsewhere)."New value: +"Commands to run in the folder (PowerShell on Windows, sh elsewhere). Prefer a list: each one must succeed before the next runs."
    • removedInput schema / properties / command / type
      Removed value: -"string"
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Adds genuinely useful behavioral facts beyond the annotations: execution happens in a fresh temp folder (isolation) and halts at the first failing command (fail-fast), plus executables land on PATH. It does not disclose timeouts, network requirements, cleanup of the temp folder, or what is returned on failure, so the disclosure is partial.

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?

Two tight sentences with the key constraint (fresh temp folder, stop at first failure) front-loaded and no filler. Every clause carries information an agent needs.

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?

With no output schema and only a non-destructive annotation, the description should say more about outcomes (pass/fail reporting, where artifacts remain, timeout behavior) for a tool that spins up installs and runs arbitrary commands. The core mechanics are covered, but failure reporting is not.

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 coverage is only 20% (only 'command' is documented), so the description must compensate. It clarifies that repoUrl is an alternative to installing the published package and implies name/version/registry select that package, but leaves version/registry semantics and name's role unstated.

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?

Specific verb+resource: installs a published package (or clones repoUrl) into a fresh temp folder and runs commands in order, stopping at first failure. An agent can tell it's an end-to-end install verification rather than a raw command runner. However it never names siblings like install_tool or run_command to disambiguate.

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?

The phrase 'verify install' via fresh-folder install + command sequence implies the scenario (validate a package actually works after publishing), but there is no explicit when-to-use/when-not or comparison to install_tool/run_command/run_checks. Usage must be inferred from the workflow shape.

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