Skip to main content
Glama

Update account details

account_update
Idempotent

Updates the workspace name, from name, reply-to address or the physical footer address (required by law in marketing email). Uses no quota. Reversible by setting the old value again. Billing can never be changed here. Confirm the new values with the person first. Requires API key scope: account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "account_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
reply_toNoWhere replies go.
from_nameNoName recipients see in the From field.
footer_addressNoPhysical mailing address printed in every campaign footer.
workspace_nameNoWorkspace or business name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the call consumes no quota, that changes are reversible by re-setting the old value, that billing fields are permanently out of scope, and that an account-scoped API key is required. This is exactly the kind of context annotations (readOnly=false, idempotent=true, destructive=false) cannot convey.

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?

Five short sentences, each carrying distinct information (capability, quota, reversibility, exclusion, prerequisite). Zero filler and the scope/prerequisite content is front-loaded.

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 four-parameter, all-optional mutation with no output schema, the description covers cost, reversibility, authorization, scope limits, and a procedural caution. There is nothing material an agent needs in order to invoke it safely that 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 description coverage is 100%, so the baseline is 3; the description adds meaning by explaining why footer_address exists (legally required in marketing email) rather than only where it is printed. It does not describe the email format or length constraints, leaving those entirely to 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 (updates) and enumerates the exact resources affected: workspace name, from name, reply-to address, and physical footer address. It also explicitly excludes billing, which separates it from the billing-related siblings without needing to name them.

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 operational guidance: confirm new values with the person first, and requires the 'account' API key scope. It also states a hard exclusion (billing can never be changed here) but does not name an alternative tool for cases the agent might actually want, such as reading current values via account_get.

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