Skip to main content
Glama
Systems Manager

Systems Manager

Add Repository

sm_system_add_repository
Destructive

Adds a repository by URL or name, enabling managed systems to install and update packages from that source.

Instructions

Add repository (sm_system_operations). System operations for managing packages, system health, and updates

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sm_system_add_repository"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
repositoryNoRepository URL or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say that the repository entry is persisted into system package configuration, whether elevated privileges are needed, whether an existing entry would be overwritten, or that repeated calls create duplicates (consistent with non-idempotency). With annotations present the bar is lower, but zero added behavioral context warrants a 2.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the action, which is good. But the second sentence is generic category filler that consumes roughly half the text without informing tool selection, making the definition under-informative rather than genuinely concise.

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?

This is a destructive, non-idempotent system mutation with no output schema, and the description omits what changes on disk, what a successful response indicates, and whether privileges are required. Annotations cover the risk flags but not the operational consequences, leaving a meaningful gap for a write tool.

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 100%, so both `repository` and `confirm` are already documented in the schema, which sets the baseline at 3. The description adds no format hints (URL vs. name resolution) and no guidance on when to pass `confirm`, so it neither compensates nor detracts.

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

Purpose3/5

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

The name and first clause do state a verb and resource ('Add repository'), so the basic action is identifiable. However, the parenthetical '(sm_system_operations)' and the follow-up 'System operations for managing packages, system health, and updates' merely restate a category rather than clarifying what kind of repository (package source, URL, mirror) is being added. Nothing distinguishes it from siblings such as sm_system_update or sm_system_install_local_package.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or follow-up tools (e.g., updating or listing packages after adding a repo). The agent must infer the use case entirely from the name.

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