Skip to main content
Glama

Rename app

renameProject
Idempotent

Rename one owned project — the Settings page’s own Save, for the name alone; it is the fix for a name chosen badly when the code arrived. Nothing else changes: the code, the live address, the deployments, the database and every domain connection stay exactly as they are, and so do the environment settings, except that before the app’s first deploy a public setting holding the address that deploy would give it moves to the new name’s address. That is why it needs no confirmation and takes no confirmed field. A name carrying what looks like a credential or a token is refused. The answer is the project’s settings row, as the Settings page reads it back after saving. It cannot rename another account’s project, which answers exactly as the dashboard does.

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": {
      "projectId": "<projectId>",
      "name": "<name>"
    },
    "name": "renameProject"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
nameYes
sourceYes
createdAtYes
frameworkYes
projectIdYes
deploymentPendingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, idempotent, non-destructive), the description discloses the exact blast radius, an unusual conditional side effect (the pre-first-deploy public address setting is moved to the new name's address), the absence of a confirmation requirement, the credential/token name refusal, and the permission boundary for other accounts. This is precisely the extra context annotations cannot carry.

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 purpose is front-loaded, but the text is one long em-dash-chained sentence with dense parenthetical detail about the pre-deploy address setting. That detail earns its place, yet the packaging makes it harder to scan than a short structured list would.

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 two-parameter mutation with an output schema, the definition covers permissions, side effects, validation rules, confirmation behavior, and what the response represents (the settings row as the Settings page reads it). Nothing an agent needs before calling 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?

With 0% schema description coverage, the description must compensate, and it does for the key semantics: 'projectId' must be an owned project, and 'name' is rejected if it resembles a credential or token — a rule absent from the schema's pattern/maxLength constraints. It does not discuss the 80-character limit or character pattern, but the schema covers those.

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 first clause gives a specific verb and resource ('Rename one owned project') and immediately scopes it ('for the name alone'), explicitly ruling out the code, address, deployments, database and domains. An agent can tell this is not a general project-update tool without inspecting the schema.

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?

It states the motivating use case ('the fix for a name chosen badly when the code arrived') and a scope exclusion ('cannot rename another account's project'), plus the fact that no confirmation step is needed. It does not name an alternative tool for broader settings changes, so it falls short of a full when/when-not/alternative triad.

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