billforward-mcp

update-account

Update an existing account's profile by providing account ID and updated fields like email, first name, last name.

Instructions

Update an existing account profile. Billforward uses PUT for updates, so pass all relevant profile fields.

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": {
      "accountId": "<accountId>",
      "profile": "<profile>"
    },
    "name": "update-account"
  }
}

Input Schema

Name	Required	Description	Default
`profile`	Yes	The updated profile fields
`accountId`	Yes	The UUID of the account to update

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jul 1, 2026

TDQS

A3.9/5.0

Behavior2/5

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

Without annotations, the description carries full transparency burden. It discloses the PUT update behavior but omits details on error states, idempotency, authentication needs, or consequences of missing fields beyond the PUT requirement.

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?

Two sentences with no wasted words. First sentence states the core purpose, second provides critical implementation guidance. Front-loaded and efficient.

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?

Adequate for a simple mutation tool with 2 params and no output schema. Covers the main behavioral point (PUT update) but lacks context on error handling, required permissions, or response format.

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. The description adds value by emphasizing that all relevant profile fields must be passed due to PUT semantics, going beyond the schema's individual field descriptions.

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?

Clearly states it updates an existing account profile, specifying the verb 'Update' and the resource. Distinguishes from siblings like create-account and get-account by focusing on modification of an existing entity.

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 key usage guideline about PUT semantics requiring all relevant profile fields, which helps prevent partial updates. However, it does not explicitly contrast with sibling tools or list when not to use.

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