Skip to main content
Glama

Preview config change

preview_config_change
Read-only

Preview project, service, or pipeline config upserts before applying, without writing YAML. See the exact change for review and approval.

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.
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
Behavior3/5

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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds 'without writing YAML' which gives some context about side effects, but it doesn't explain what the preview actually returns, whether it validates, or how it differs from a real upsert in behavior. Given the annotation, the bar is lower, and the small extra context earns a 3.

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 sentence, front-loaded with the core purpose. There is zero waste, and it is easy to parse.

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?

With 9 parameters, nested objects, no output schema, and only 22% schema description coverage, the description is too sparse to be complete. It does not describe the preview result format, dependencies between parameters, or when to provide approval_token or debug_session_id. The tool is more complex than the description addresses.

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 information. Schema description coverage is only 22%, and while the pipeline and service properties have detailed inline descriptions, the tool description itself does not compensate for the low coverage. Parameters like kind, root_path, project_id, and approval_token are left entirely to the schema, which lacks descriptions for most.

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's function: 'Preview a project/service/project-pipeline config upsert without writing YAML.' This uses a specific verb ('Preview') and resource ('config upsert'), and distinguishes it from sibling tools like apply_config_change or upsert_project_config by emphasizing that it does not write YAML.

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 provides no guidance on when to use this tool versus alternatives. It does not mention using it before applying changes or that it is the safe counterpart to apply/upsert tools. No explicit when-to-use or exclusion criteria are given.

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