Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

edit_config

Destructive

Read or atomically replace a regular configuration file on a remote server, with local write permission required and private backups enabled by default.

Instructions

Read or atomically replace a regular config file. Writes require local permission; unique private backups are enabled by default.

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": {
      "server": "<server>",
      "path": "<path>"
    },
    "name": "edit_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
backupNo
serverYes
contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), it adds real behavioral context: writes are atomic, they require local permission, and unique private backups are on by default. It stops short of saying what a failed write leaves behind or how a backup is identified/restored, which would matter for a destructive tool.

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 dense sentences with no filler: the read/replace behavior comes first, then the write-time constraints. Every clause (atomic, local permission, backups default on) carries information the 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?

For a destructive, four-parameter tool with no output schema and zero schema descriptions, the definition covers safety and atomicity well but leaves the required 'server' parameter and the read-mode return shape unaddressed. Adequate but with a meaningful hole.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema explains nothing and the description must compensate. It clarifies the backup default and implies content drives write mode, but the required 'server' parameter is never mentioned and there is no explanation of what path values are accepted or what a null content means formally.

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?

The description names a concrete verb pair and resource: read or atomically replace a regular config file. It is clear what the tool operates on and that there are two modes, though it does not explicitly contrast itself with sibling tools (the siblings listed are mostly checks/session tools, so overlap is low).

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?

Usage is only implied: a reader must infer that reading happens without content and replacement happens when content is supplied. There is no explicit when-to-use statement, no prerequisites, and no guidance on choosing this over create_backup or execute_command for file manipulation.

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