Skip to main content
Glama

Patch MCP

update_account

Destructive

Update supplied profile, language, voice and pronunciation defaults using the revision from get_account. Each number's voice system is set with update_phone_number. Language and voice defaults require configuration permission. Internal system prompts are not exposed through MCP.

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": {
      "revision": "<revision>",
      "changes": "<changes>"
    },
    "name": "update_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
revisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / changes / properties / mode
      Removed value: -{
      -  "enum": [
      -    "standard",
      -    "beta"
      -  ],
      -  "type": "string"
      -}
  2. Changed4 schema fields changed
    • addedInput schema / properties / revision / anyOf
      Added value: +[
      +  {
      +    "pattern": "^account_[a-f0-9]{64}$",
      +    "type": "string"
      +  },
      +  {
      +    "format": "date-time",
      +    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / revision / format
      Removed value: -"date-time"
    • removedInput schema / properties / revision / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
    • removedInput schema / properties / revision / type
      Removed value: -"string"
  3. Changed1 schema field changed
    • addedInput schema / properties / changes / properties / pronunciation_overrides
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "pronunciation": {
      +        "maxLength": 100,
      +        "minLength": 1,
      +        "pattern": "^[\\p{L}\\p{M}\\p{N} .’'-]+$",
      +        "type": "string"
      +      },
      +      "word": {
      +        "maxLength": 64,
      +        "minLength": 1,
      +        "pattern": "^[\\p{L}\\p{M}\\p{N} .’'-]+$",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "word",
      +      "pronunciation"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / changes / properties / mode
      Added value: +{
      +  "enum": [
      +    "standard",
      +    "beta"
      +  ],
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • removedInput schema / properties / changes / properties / agent_instructions
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "maxLength": 20000,
      -      "minLength": 1,
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ]
      -}
  6. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a destructive, non-idempotent, non-read-only mutation, and the description adds real context: configuration permission is required and internal system prompts are walled off. It does not disclose the merge-vs-replace semantics of 'changes', whether omitted fields are preserved, or how a stale revision fails, which matters for a destructive non-idempotent write.

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 dense sentences, front-loaded with the action and its data source, then constraints and exclusions. No filler; the only friction is that 'Each number's voice system' requires the reader to infer it refers to phone numbers.

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

Completeness3/5

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

Output schema exists, so return values need no explanation, and permissions plus the prompt-exposure exclusion are covered. For a destructive, non-idempotent two-parameter mutation with fully nested, undocumented properties, the missing piece is update semantics and failure behavior on revision mismatch.

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 0%, so the description must compensate: it does explain that 'revision' originates from get_account and maps the nested 'changes' properties to prose terms (name/profile, call_locale/language, voices_by_locale/voice, pronunciation_overrides/pronunciation). It stops short of describing value formats, the locale key shape in voices_by_locale, or whether changes are partial or full replacement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and enumerates the resource categories it touches (profile, language, voice, pronunciation defaults), which lets an agent distinguish it from update_phone_number, named explicitly for per-number voice settings. Slightly short of 5 because the term 'defaults' is doing ambiguous work about whether account-level settings cascade.

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 a concrete prerequisite ('using the revision from get_account') and names the alternative for the adjacent case ('Each number's voice system is set with update_phone_number'), plus a permission condition. No explicit when-not guidance beyond that redirect, but the routing information is clear.

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