Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Add item to acquisition

add_acquisition_items

Add one firearm to a pending acquisition by providing the acquisition ID and required firearm details, so the item is recorded before the acquisition is committed.

Instructions

Add a single firearm to a pending acquisition. Executes directly (the acquisition is still uncommitted). 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": {
      "acquisitionId": "<acquisitionId>",
      "manufacturer": "<manufacturer>",
      "model": "<model>",
      "serial": "<serial>",
      "caliber": "<caliber>",
      "type": "<type>"
    },
    "name": "add_acquisition_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
mpnNo
skuNo
upcNo
costNo
noteNo
typeYesRequired. See list_smartlists ItemType.
modelYesRequired.
priceNo
serialYesRequired. The serial marked on the firearm.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
caliberYesRequired. See list_smartlists Caliber.
importerNoRequired for imported firearms.
locationNoSee list_smartlists Location.
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.
conditionNoSee list_smartlists Condition.
externalIdNo
itemNumberNo
totalLengthNo
barrelLengthNo
manufacturerYesRequired. See list_smartlists Manufacturer.
acquisitionIdYesGUID of the pending acquisition.
countryOfManufactureNo

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

B3.1/5.0
Behavior3/5

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

Annotations only supply destructiveHint=false; the description adds real value by disclosing that the call 'executes directly' because the acquisition is still uncommitted, telling the agent no separate commit is needed for this step. It omits validations that matter for a 22-parameter write, such as whether added items can be removed before commit, what happens on duplicate serials, or audit-trail side effects.

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 short sentences, front-loaded with the action and followed by the execution model. The trailing 'Write.' is redundant with the title and destructiveHint annotation, but the overall size is well matched to a quick-reference gloss.

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

Completeness2/5

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

For a 22-parameter mutation with no output schema and only one weak annotation, the description is far too thin. An agent gets no guidance on the six required fields as a group, on optional-but-important fields, or on what the call returns or how errors surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 22 parameters and only 50% schema description coverage, the description must compensate, but it adds nothing beyond 'single firearm'. It never explains key semantics like the per-call account override, the auditUser ATF trail behavior, importer requirements, or how cost/price strings are interpreted, leaving half the surface documented nowhere.

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 resource: 'Add a single firearm to a pending acquisition.' The word 'single' implicitly distinguishes it from bulk item operations, and 'pending acquisition' scopes it apart from item updates and dispositions, though it does not name a sibling explicitly.

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 phrase 'the acquisition is still uncommitted' implies this belongs before commit_acquisition, but the description never says when to use this versus update_acquisition_item or add_disposition_items, nor does it state prerequisites such as needing an existing acquisitionId from create_pending_acquisition.

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