Skip to main content
Glama

Apply config change

apply_config_change

Apply project, service, or pipeline configuration changes through the local agent safe-operation flow, requiring human approval.

Instructions

Apply a config upsert through the local agent safe-operation flow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
projectNo
serviceNoService config. Set service.language (go, node, python) as the service implementation language; it is required for local managed runtime.type=language deployments. For remote deployments, deployments[].host_ids must contain canonical non-self Host.id values returned by list_hosts, not host name/display name. Set deployments[].ports (array of ints) to declare the ports a deployment listens on; for a project homed on a dev machine this is what makes SuperDev mirror those ports back to 127.0.0.1 on the control-plane machine.
pipelineNoProject pipeline config. Key fields: `variables` are pipeline-wide defaults (strings). `environments` is a map of env name -> { variables } that OVERRIDE defaults per environment (precedence: project < pipeline < pipeline.pipeline < environments[env] < run vars); the same pipeline serves multiple environments by overriding only the differing variables. `sync_mode` declares how build artifacts reach targets: "transfer" (agent uploads the packaged artifact) or "remote_cmd" (the target host runs a command such as git pull to fetch code itself); empty defaults to transfer. `roles` maps a role/run-group name to a host list (run groups); a role entry uses {from_service} to derive hosts from a service's deployment for the running env, or {hosts:[...]} for an explicit set. Only plugins that need to target a specific group (e.g. nginx upstream) reference roles; most deploy steps follow the env deployment targets automatically. Any host_ids, roles hosts, or task host_id values must use canonical non-self Host.id values returned by list_hosts, not host names.
root_pathNo
project_idNo
project_nameNo
approval_tokenNo
debug_session_idNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.2.4
    • changedInput schema / properties / service / description
      Previous value: -"Service config. Set service.language (go, node, python) as the service implementation language; it is required for local managed runtime.type=language deployments. For remote deployments, deployments[].host_ids must contain canonical non-self Host.id values returned by list_hosts, not host name/display name."New value: +"Service config. Set service.language (go, node, python) as the service implementation language; it is required for local managed runtime.type=language deployments. For remote deployments, deployments[].host_ids must contain canonical non-self Host.id values returned by list_hosts, not host name/display name. Set deployments[].ports (array of ints) to declare the ports a deployment listens on; for a project homed on a dev machine this is what makes SuperDev mirror those ports back to 127.0.0.1 on the control-plane machine."
  2. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. 'Apply' implies mutation and 'safe-operation flow' hints at an approval gate, but the description does not explain side effects, required approval tokens, reversibility, or failure behavior. This is a significant transparency gap for a write operation.

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?

The description is a single sentence with no wasted words, so it is concise. However, it is under-specified to the point of being minimally informative, and it does not cover the complexity of a 9-parameter tool with nested objects.

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

Completeness1/5

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

This is a complex mutating tool with no annotations, no output schema, and low parameter coverage. The description does not explain the safe-operation workflow, approval requirements, the meaning of kind, or what happens when the change is applied. An agent cannot reliably select and invoke this tool based on the description alone.

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

Parameters1/5

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

Schema description coverage is only 22%, and the description adds no parameter-level meaning. It does not mention kind, project, service, pipeline, approval_token, or any of the other eight parameters. The detailed descriptions present in the schema for service and pipeline are not reinforced or summarized in the description.

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 identifies a specific action ('apply') and a resource ('config upsert'), and mentions the 'safe-operation flow' which separates it from direct upsert siblings. However, it does not explicitly state which config types (project/service/pipeline) are covered, and relies on the schema's kind enum for that specificity.

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?

The description gives no explicit guidance on when to use this tool versus sibling tools like upsert_project_config, preview_config_change, or get_operation_approval. The phrase 'safe-operation flow' implies it is for applying pre-approved changes, but no when-to-use or when-not-to-use conditions are stated.

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/Xsxdot/super-dev'

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