Skip to main content
Glama

Configure runtime settings

configure_dynamic_project
DestructiveIdempotent

Updates an application project’s runtime settings, non-secret defaults, variable enablement and scheduled tasks. Manifest changes can rebuild retained source; variable changes can restart the app. Failed operations restore prior settings and data.

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": {
      "project_id": "<project_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "configure_dynamic_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestNoRead runtime_contract first. Omitted settings retain the existing project configuration. PHP start is empty for the managed server.
schedulesNo
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
environmentNo
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.
build_environmentNo
environment_updatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing concrete consequences: manifest changes can rebuild retained source, variable changes can restart the app, and failed operations restore prior settings and data. The rollback guarantee meaningfully qualifies the destructiveHint=true annotation, telling the agent the blast radius is recoverable. It stops short of stating permission requirements or latency/timing of rebuilds.

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?

Three tight sentences, front-loaded with the operation then the side effects then the safety net. Every sentence carries distinct information with no filler.

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, nested-schema mutation with no output schema, the description covers side effects and rollback but omits idempotency-retry guidance and the ordering prerequisite for runtime_contract, both of which remain buried in schema fields. Adequate but not complete.

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?

At 43% schema coverage across 7 mostly nested parameters, the description only partly compensates, mapping categorically to manifest, environment defaults, variable enablement, and schedules. It adds no meaning for idempotency_key, project_id, or the environment vs build_environment vs environment_updates distinction, which are the highest-risk parameters here.

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?

States a specific verb ('Updates') and resource ('application project's runtime settings') and enumerates the four domains touched: runtime settings, non-secret defaults, variable enablement, and scheduled tasks. An agent can distinguish this write tool from read siblings like get_dynamic_project and runtime_contract, though no sibling is named in the description itself.

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 implied by the 'Updates' framing and the enumerated settings domains, so an agent can infer this is the mutation path for project runtime config. However, there is no explicit when-to-use/when-not guidance and the critical prerequisite (read runtime_contract first, resolve project_id) lives only in the schema descriptions, not the tool description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources