Skip to main content
Glama

Valet

by io.github.valetdotdev
OverviewDiscussionsAdmin

Rename a website, app, or agent

rename_service
Destructive

Rename a website, app, or agent. A website or app moves to https://..valet.run; the old address stops serving it and its name becomes available to another service in the same organization. An agent keeps its channels, which address it by id, and has no address to move. The architect agent cannot be renamed, and renaming an agent requires the organization to have one. Pass kind to say which you mean; a name holding another kind is then refused rather than renamed. Requires connecting a Valet account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoThe kind you mean. Omit to rename whatever the name holds; give it to have a name holding another kind refused.
nameYesRequired. The website's, app's, or agent's current name.
new_nameYesRequired. The new name. It also becomes the first host label of the new URL.
org_nameNoThe Valet organization it belongs to. Omit to use the organization the account joined first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "site",
-  "app"
-]New value: +[
+  "site",
+  "app",
+  "agent"
+]
    • changedInput schema / properties / name / description
      Previous value: -"Required. The website's or app's current name."New value: +"Required. The website's, app's, or agent's current name."
  2. Changed1 schema field changed
    • changedInput schema / properties / new_name / description
      Previous value: -"Required. The new name. It also becomes the last path segment of the new URL."New value: +"Required. The new name. It also becomes the first host label of the new URL."
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only flag destructiveHint=true; the description explains exactly what is destroyed and what replaces it: the site/app moves to a new URL, the old address stops serving it, and the old name becomes available to another service. It also discloses that agents keep their channels and have no address, plus auth and eligibility constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then layers behavior, restrictions, and prerequisites in a tight sequence without filler. It is dense but every clause carries information; the only mild cost is that the restriction list reads as a run-on.

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 destructive mutation with no output schema and no annotations beyond the safety flags, the description covers the side effects, identity/eligibility constraints, and auth requirement an agent needs before invoking it. Nothing material is left implicit.

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?

Schema description coverage is 100%, so each parameter including the kind enum is already documented. The description's note about passing kind largely restates the schema text, and org_name is never addressed, so it adds only marginal value over structured data.

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 (rename) plus the three resources it operates on (website, app, agent), and no sibling tool competes for that purpose. An agent can distinguish it from destroy_service, publish_site, or share_service without opening any 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?

Gives concrete conditions: pass kind to disambiguate, a name holding another kind is refused rather than renamed, the architect agent cannot be renamed, and renaming an agent requires the org to have one. It also states the prerequisite of a connected Valet account. It stops short of naming a sibling alternative for edge cases, so not a full 5.

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

All Valet toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources