Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Acquire (create + commit)

acquire

Records a firearm acquisition into the A&D book with supplier contact details. Provides a dry-run preview by default; set confirm:true to execute the write.

Instructions

Record an acquisition and commit it to the A&D book in one step (the recommended intake path). A supplier contact is REQUIRED — provide contactId, contactExternalId, or an inline contact. This commits a regulated record: dry-run by default, pass confirm:true to execute. Write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoAcquisition date (ISO). Defaults to now if omitted.
noteNo
typeYesAcquisition type (required). See list_smartlists AcquireType.
itemsYesFirearms being acquired into the A&D book.
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 supplier contact (alternative to contactId).
auditUserNoEmail recorded as X-AuditUser for the ATF audit trail. Overrides FASTBOUND_AUDIT_USER for this call. Must be an active user on the account.
contactIdNoExisting supplier contact GUID.
externalIdNo
invoiceNumberNo
contactExternalIdNoExisting supplier contact externalId.
purchaseOrderNumberNo
shipmentTrackingNumberNo
isManufacturingAcquisitionNoFFL type 07/10 manufacturing only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Beyond annotations (only destructiveHint: false), the description discloses important behavior: this commits a regulated record, it is dry-run by default, and confirm:true is required to execute. The final 'Write' clarifies that this is a mutating call despite the non-destructive hint. It could add more about side effects or failed dry-runs, but the core behavioral traits are clearly stated.

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?

The description is compact and front-loaded with the main purpose, followed by the required-contact rule and the dry-run/confirm behavior. The final standalone 'Write.' is slightly redundant, but the overall description is efficient and every substantive sentence serves a clear purpose.

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 a complex tool with 15 parameters, nested objects, and no output schema, the description covers the most critical operational facts: what the tool does, the mandatory contact requirement, and the dry-run default. It doesn't describe response formats or edge-case behavior, but an agent has enough context to select the tool and invoke it safely without unintended commits.

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 67%, so the schema covers most parameters, but the description adds high-value meaning by explaining that a supplier contact is REQUIRED and enumerating the three acceptable ways to provide it (contactId, contactExternalId, or inline contact). It also reinforces the confirm parameter's crucial role in executing vs. previewing, which helps the agent avoid an unintended commit.

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 uses a specific verb-resource pairing: 'Record an acquisition and commit it to the A&D book in one step.' It clearly names the combined create+commit behavior and calls it the 'recommended intake path,' which distinguishes it from siblings like create_pending_acquisition and commit_acquisition.

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?

The description gives explicit context for use: it is the recommended one-step path and requires a supplier contact via contactId, contactExternalId, or an inline contact. It also explains the dry-run vs. execute flow with confirm:true. It doesn't explicitly name when to prefer the separate pending/commit siblings, but the 'one step' recommendation makes the intended use clear.

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

Deploy Server

Other Tools