Skip to main content
Glama

Update account name or company name

update_account
DestructiveIdempotent

Change the account holder's name or the company name. Recipients see emails from " via md2sign", or the person's own name when there is no company name, so fix these before sending if they are wrong. Only the company admin can change the company name; an empty company_name removes it.

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": "update_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe account holder's full name, as they want it shown to recipients.
api_keyNoAn md2sign API key. When given, this call uses that key's account even if the connection is signed in as someone else, so pass it on every call when your human has more than one md2sign account (for example two businesses). Also use it if your MCP client cannot send an "Authorization: Bearer <api_key>" header.
company_nameNoThe business name recipients see, e.g. "Law Garden Design". Pass an empty string to remove it and use the person's own name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds real value on top: the admin permission requirement and the fact that an empty company_name removes the value (consistent with the destructive annotation). It also discloses the recipient-visible consequence of the change, though it says nothing about what happens when both fields are omitted.

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?

Three tight sentences, front-loaded with the core action, then the consequence, then the constraints. The clause 'so fix these before sending if they are wrong' is mildly editorial but earns its place as motivation for the call.

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

Completeness4/5

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

For a three-optional-parameter mutation tool with no output schema, the description covers permissions, side effects, and the visibility impact of the values. The one gap is that it never states that at least one of name or company_name must be supplied, which matters given zero required parameters.

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 coverage is 100%, so all three parameters including the api_key routing behaviour are already documented in the schema. The description restates the empty-string removal semantics for company_name and the recipient-visibility meaning of name, but adds no syntax or format detail beyond the schema — the baseline 3 applies.

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 ('Change the account holder's name or the company name') and enumerates exactly the two editable fields, which an agent can immediately distinguish from create_account and get_account. It also explains the downstream effect on what recipients see, removing any ambiguity about what the change means.

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?

Provides a clear condition for use ('fix these before sending if they are wrong') and a hard prerequisite ('Only the company admin can change the company name'). It does not explicitly name alternatives such as create_account for setting up a new account, but the context is strong enough that no exclusion is really needed.

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.