Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update item

update_item
Idempotent

Edit an existing firearm record by updating only the specified fields, leaving others unchanged. Preview changes with a dry run, then confirm to apply.

Instructions

Edit fields on an existing firearm record. Performs a read-merge-write so unspecified fields keep their current values. Dry-run by default (preview shows the merged body); pass confirm:true to apply. Write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFastBound GUID of the item to edit.
mpnNo
skuNo
upcNo
costNo
noteNo
typeNo
modelNo
priceNo
serialNo
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
caliberNo
confirmNoSet true to actually execute. Omit or false returns a DRY RUN preview that sends nothing.
importerNo
locationNo
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.
conditionNo
externalIdNo
itemNumberNo
totalLengthNo
acquire_DateNo
barrelLengthNo
doNotDisposeNo
manufacturerNo
acquisitionTypeNo
countryOfManufactureNo
acquire_InvoiceNumberNo
acquire_PurchaseOrderNumberNo
acquire_ShipmentTrackingNumberNo

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

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

Goes well beyond the idempotentHint and destructiveHint annotations by disclosing read-merge-write semantics, preservation of unspecified fields, dry-run default behavior, and the confirm:true requirement. This is strong, actionable operational detail.

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 that front-load the core purpose and then add behavioral detail. The trailing 'Write.' is a minor redundancy but does not meaningfully hurt clarity.

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

Completeness3/5

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

The core call semantics are covered, including the critical dry-run and merge behavior. However, with 29 parameters, low schema coverage, and no output schema, an agent still lacks detail about return values and the meaning of many fields.

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?

Schema description coverage is only 14%, and the description does not compensate by explaining the many undocumented string/number fields. It adds useful global merge and confirm semantics, but most parameter meaning is left to the parameter names.

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?

Opens with a specific verb and resource: 'Edit fields on an existing firearm record.' This clearly distinguishes it from sibling update_* tools that target acquisitions, dispositions, and contacts, so an agent can select it without opening schemas.

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?

Explains the read-merge-write behavior and the dry-run-by-default / confirm:true flow, giving practical guidance on how to call it safely. It does not explicitly list alternatives or when not to use it, but the usage context is clear enough.

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