Skip to main content
Glama
Partiri-Cloud

Partiri Cloud MCP Server

Get Partiri CLI Guidance

use_partiri_cli
Read-onlyIdempotent

Get step-by-step instructions to run the Partiri Cloud CLI locally for managing workspace secrets, detaching or deleting volumes, killing services, and managing service environment variables.

Instructions

Guidance for running the locally-installed partiri CLI yourself for sensitive operations that are intentionally not exposed as direct MCP tools: managing workspace secrets (partiri secret create-repository / create-registry), detaching or deleting a volume (partiri storage detach / delete), killing a service (partiri service kill), and managing service environment variables (partiri service env). This tool does NOT execute anything — it returns instructions for you to run the command in your own shell. These operations are kept CLI-only because they pass long-lived credentials or cause irreversible data loss, and the CLI authenticates independently of the MCP session. Note: creating, attaching, or retry-provisioning a volume has no CLI subcommand — use the dashboard or API. Service-scoped commands like service kill read the service ID from a local .partiri.jsonc (only service deploy accepts --service <UUID>). Discover exact subcommands and flags at runtime — run partiri llm guide, partiri llm capabilities -j, or partiri <area> --help first; do not assume command syntax. For credential values prefer stdin (with the CLI flag that reads stdin, e.g. --token-stdin / --password-stdin) over an argument so the secret stays out of the command line and this context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhat you want to accomplish with the partiri CLI, e.g. "delete a service".
commandNoThe specific partiri CLI command to run, if known, e.g. "partiri service kill".
Behavior5/5

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

Discloses that the tool returns instructions, does not execute anything, and explains why (long-lived credentials, irreversible data loss, independent auth). Adds context about service-scoped commands reading service ID from local file. No contradiction with 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 long but well-structured and front-loaded with the core purpose. Each sentence adds necessary context. Minor verbosity in listing all operations but overall efficient for the detail provided.

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

Completeness5/5

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

Given the complexity, no output schema, and rich annotations, the description covers usage guidelines, alternatives, caveats, discovery instructions, and best practices. It is fully adequate for an agent to decide when and how to invoke this tool.

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%, baseline 3. Description adds value by explaining the purpose of each parameter, e.g., 'action' describes what to accomplish, 'command' provides an optional specific command. Gives examples and best practices for stdin usage.

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 tool provides guidance for running CLI commands for sensitive operations, not executing them. It lists specific CLI subcommands and distinguishes itself from sibling tools by explaining these operations are intentionally not direct MCP tools.

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

Usage Guidelines5/5

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

Explicitly states when to use (for sensitive CLI-only operations) and when not to (e.g., creating/attaching a volume uses dashboard/API). Provides alternatives like using the dashboard or API. Also advises to discover command syntax via runtime help commands.

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/Partiri-Cloud/harbor-mcp'

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