Skip to main content
Glama

Preview config change

preview_config_change
Read-only

Preview config upserts for projects, services, or pipelines to validate changes before writing YAML.

Instructions

Preview a project/service/project-pipeline config upsert without writing YAML.

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

B3.4/5.0
Behavior3/5

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

The annotation declares readOnlyHint: true, so the safe read-only nature is already known. The description adds the detail 'without writing YAML', which reinforces that no file is written, subtly exceeding the annotation. However, it does not disclose what the preview returns (e.g., a diff, validation errors, or a rendered config) or any other behavioral traits. Since the annotation sets a lower bar and the description adds one useful piece of context, a 3 is fair with no contradiction.

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?

The description is a single, well-structured sentence that front-loads the primary purpose (preview) and clearly distinguishes it from write operations. There is zero waste; every word contributes to the core meaning. This is an exemplar of conciseness.

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?

Given the tool's complexity (9 parameters, nested objects, 22% schema coverage, and no output schema), the description is far too sparse. It lacks information on what the preview actually returns, how to interpret results, or how it relates to apply_config_change and upsert tools. An agent would struggle to know what to do with the output or how to properly construct a request beyond the schema hints. This is inadequate for the operational context.

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?

The description provides no parameter-level information; it is entirely silent on the meaning of kind, project, root_path, project_id, etc. While the schema itself contains rich descriptions for service and pipeline, those are part of the schema, not the description. With schema description coverage at only 22%, the description does nothing to compensate for undocumented parameters. This leaves agents guessing on most parameters, so a 2 is warranted.

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 'Preview a project/service/project-pipeline config upsert without writing YAML' clearly identifies the verb (preview), the resource (config upsert), and the scope (project/service/project-pipeline). It distinguishes this from actual upsert tools by stating 'without writing YAML', which separates it from siblings like upsert_project_config. However, it does not explicitly name alternative tools, so it earns a 4 rather than a 5.

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

Usage Guidelines4/5

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

The phrase 'without writing YAML' implies this is for dry-run or inspection before actually applying a change, which gives clear context for when to use it versus upsert or apply tools. It does not explicitly state when not to use it or name specific alternatives, but the purpose is inferable. Given that the description is brief yet the intent is clear, a 4 is appropriate.

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