Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Commit disposition

commit_disposition

Commit a pending A&D disposition by setting confirm:true; the default dry run previews changes, and execution may trigger a Multiple Sale report or create an FFL recipient acquisition.

Instructions

Commit a pending disposition to the A&D book — the point of no return. May trigger a Multiple Sale report and, for FFL transfers, auto-create the recipient's acquisition (reported via headers). Dry-run by default; pass confirm:true. 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_disposition"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGUID of the pending disposition 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.
otherTransfereeEmailsNoRecipient FFL user emails for an FFL transfer.

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.4/5.0
Behavior5/5

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

Goes well beyond the single destructiveHint annotation by disclosing side effects: a possible Multiple Sale report trigger, auto-creation of the recipient's acquisition for FFL transfers with those results surfaced via headers, and the irreversible nature of the commit. The dry-run default is a critical behavioral fact that the annotations do not 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?

Four short sentences, front-loaded with the action and its consequence, then the side effects, then the safety gate. No filler and nothing an agent must skim past to find the confirm:true requirement.

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?

Given no output schema, the description still explains what the call may produce (a Multiple Sale report, an auto-created acquisition, header-reported results), which is the most important return behavior. Remaining gaps — error modes and whether a commit is idempotent — are minor for a confirm-gated write.

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 100%, so id, account, confirm, auditUser and otherTransfereeEmails are already fully documented. The description only reinforces the confirm/dry-run semantics and points at list_accounts for account aliases, adding little beyond the structured fields; 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 disposition to the A&D book' — with a scope note ('point of no return') that separates it from the sibling commit_acquisition and from preparatory tools like lock_disposition or add_disposition_items. 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 Guidelines4/5

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

Gives the precondition ('pending disposition') and the execution gate ('Dry-run by default; pass confirm:true'), which tells the agent exactly how to get a safe preview versus a real commit. It does not name alternatives or exclusions (e.g., when to use commit_acquisition instead), leaving that to be inferred.

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