Skip to main content
Glama

Rename application environment

rename_application_environment
Destructive

Rename one environment of an Application. Only the name changes: the environment's id, role, order and deployments stay as they are. A name another environment holds, or one that is a cluster's name, is refused. Needs applications.write.

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": {
      "application_id": "<application_id>",
      "environment_id": "<environment_id>",
      "name": "<name>"
    },
    "name": "rename_application_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name.
application_idYesThe Application's id.
environment_idYesThe environment's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: only the name changes, id/role/order/deployments remain unchanged, invalid names are refused, and applications.write is required. This clarifies the mutation's scope and authorization needs despite the destructiveHint annotation.

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?

Four compact sentences, front-loaded with purpose and followed by invariants, validation, and permissions. No wording is wasted.

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

Completeness5/5

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

For a simple three-parameter mutation with no output schema, the description covers purpose, side effects, constraints, and authorization sufficiently. Nothing critical for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics for the name parameter by stating uniqueness and cluster-name refusal constraints, though it does not discuss the id parameters beyond the schema.

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?

States a specific verb and resource: renaming one environment of an Application. The scope is precise enough to distinguish it from other rename_* siblings by resource type.

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?

Gives clear context for when the tool applies and what changes, plus validation and permission constraints. It does not explicitly name alternatives, but the operation is specific and the description leaves little ambiguity.

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.