Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Commit acquisition

commit_acquisition

Commit a pending acquisition to the A&D book by previewing a dry run first, then passing confirm:true to execute the write.

Instructions

Commit a pending acquisition to the A&D book — the point of no return. Dry-run by default; pass confirm:true to commit. Write.

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

Input Schema

NameRequiredDescriptionDefault
idYesGUID of the pending acquisition to commit.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
confirmNoSet true to actually execute. Omit or false returns a DRY RUN preview that sends nothing.
auditUserNoEmail recorded as X-AuditUser for the ATF audit trail. Overrides the account's default audit user (FASTBOUND_<ALIAS>_AUDIT_USER, else FASTBOUND_AUDIT_USER) for this call. Must be an active user on the account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / auditUser / description
      Previous value: -"Email recorded as X-AuditUser for the ATF audit trail. Overrides FASTBOUND_AUDIT_USER for this call. Must be an active user on the account."New value: +"Email recorded as X-AuditUser for the ATF audit trail. Overrides the account's default audit user (FASTBOUND_<ALIAS>_AUDIT_USER, else FASTBOUND_AUDIT_USER) for this call. Must be an active user on the account."
  2. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "Which configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.",
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

The annotations only supply destructiveHint=false, so the description carries most of the burden and does so well: it declares the default dry-run behavior, that confirm:true is required to actually execute, and that commit is irreversible ('the point of no return'). Those are the facts an agent most needs before triggering a write and are not available in the annotations or schema.

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 short clauses with zero filler: what it does, the safety default, and the opt-in switch. The most important constraint (dry-run default) is front-loaded after the action statement.

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?

No output schema exists, and the description does not say what a dry-run preview returns versus a committed result, nor that audit trail entries are written (only the schema mentions X-AuditUser). Otherwise the write semantics, irreversibility, and opt-in flag make it sufficient to call correctly.

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% and every parameter already carries a detailed description, including confirm and auditUser semantics. The description only restates the confirm flag, so it adds little meaning beyond the schema; 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 ('Commit a pending acquisition') plus the destination ('the A&D book'), which separates it from the disposition-side sibling commit_disposition. An agent can identify the operation without opening the schema.

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

Usage Guidelines3/5

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

The description gives operational guidance for the confirm flag (dry-run unless confirm:true), which tells the agent how to invoke it safely. It does not, however, state prerequisites (e.g., that a pending acquisition must first exist via create_pending_acquisition) or name alternatives, so usage context is only implied.

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