Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Dispose (create + commit)

dispose

Record a firearm disposition (sale, FFL transfer) and commit it in one step; previews changes by default until confirm:true.

Instructions

Record a disposition and commit it in one step (sale, FFL transfer, etc.). Items reference firearms already in inventory by GUID. For FFL transfers set requestType=Regular and otherTransfereeEmails; FastBound may auto-create the receiving FFL's acquisition (reported back via headers). Commits a regulated record: 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": {
      "requestType": "<requestType>",
      "date": "<date>",
      "items": "<items>"
    },
    "name": "dispose"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDisposition date (ISO, required) — when the firearm left the premises.
noteNo
otsnNo
ttsnNoSet by FastBound when a 4473 completes — leave unset at creation (same for otsn / generateTTSN).
typeNoDisposition type label. See list_smartlists DisposeType.
itemsYesInventory items being disposed.
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.
contactNoInline new recipient contact (alternative to contactId).
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.
contactIdNoExisting recipient/buyer contact GUID.
requestTypeYesDisposition request type. Use Regular for sales/FFL transfers.
generateTTSNNoHave FastBound generate the TTSN.
invoiceNumberNo
contactExternalIdNo
purchaseOrderNumberNo
otherTransfereeEmailsNoRecipient FFL user emails for an FFL transfer; FastBound notifies them and may auto-create their acquisition.
shipmentTrackingNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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."
    • addedInput schema / properties / ttsn / description
      Added value: +"Set by FastBound when a 4473 completes — leave unset at creation (same for otsn / generateTTSN)."
  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?

Annotations only say destructiveHint=false, while the description adds critical behavior: this writes/commits a regulated record, dry-runs by default, requires confirm:true to execute, and may auto-create the receiving FFL's acquisition. Those are the high-value behavioral details an agent needs before calling it.

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?

The description is four tight sentences: purpose first, then item reference, FFL special case, and safety behavior. There is no filler, and the final 'Write.' is terse but useful as a mutation signal.

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?

For an 18-parameter nested write tool, it covers the essential selection and safety behavior, and the schema carries many field-level details. However, with no output schema it only briefly mentions headers and does not clarify remaining invocation details such as contact/account handling or specialized disposition variants.

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 67%, so the schema already documents most parameters and the description mainly repeats key ones: item GUIDs, requestType=Regular plus otherTransfereeEmails for FFL transfers, and confirm:true. It does not compensate for undocumented or ambiguous parameters such as contact versus contactId, account, or auditUser.

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?

The description states a specific verb and resource: 'Record a disposition and commit it in one step,' with sale and FFL transfer examples. The 'one step' phrasing distinguishes it from a staged create followed by a separate commit, and from commit-only siblings.

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?

It gives clear usage context for recording and committing a disposition, including FFL transfer guidance and dry-run versus confirm:true behavior. It does not name alternatives or say when to prefer specialized disposition variants, so it stops short of explicit when/when-not guidance.

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