Skip to main content
Glama

Rename the account

rename_account
DestructiveIdempotent

Use this when the user wants the FlareWarden account's own name changed: the name its members see in the sidebar and account switcher, and invitations carry. Renames it as the Account page does and returns the old and new name. Owners and admins only. Not for a site's name (use update_monitor) or a status page's (use update_status_page).

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe new name, 1 to 100 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: owner/admin authorization requirement, the fact that it returns the old and new name, and that it behaves the same as the Account page. It does not address the destructiveHint=true implication directly (that the previous name is replaced, even though it is echoed back) or idempotent behavior, but the authorization and return-value disclosures are substantive.

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 sentences, front-loaded with the trigger, then the effect and return value, then the exclusions. Every clause carries information; nothing is repeated from the annotations or schema verbatim.

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?

Single-parameter mutation with no output schema, yet the description covers the trigger, the authorization gate, the return value, and the disambiguation from the two nearest siblings. Nothing an agent needs to call it correctly 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 baseline is 3, and the description earns an extra point by giving the `name` field real semantics — it is the member-visible account name used in the sidebar, switcher, and invitations, which the schema's "new name, 1 to 100 characters" does not convey.

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+resource (rename the FlareWarden account) and pins down exactly which name is affected: the one members see in the sidebar, account switcher, and invitations. It explicitly names what it is not for (a site's name, a status page's name) and routes to the correct siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ("Use this when the user wants the FlareWarden account's own name changed") and closes with two named exclusions plus the alternative tools to use instead (update_monitor, update_status_page). An agent can route correctly without opening any schema.

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