Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete item

delete_item
Destructive

Delete a firearm record from FastBound when it is a duplicate or error. Requires a delete type and audit note; previews by default and executes only with confirm:true.

Instructions

Delete a firearm record. ATF permits deletion only for a Duplicate or Error; a deleteType and an explanatory deleteNote are required and form an immutable audit entry. Dry-run by default; pass confirm:true to delete. Destructive write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFastBound GUID of the item to delete.
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 FASTBOUND_AUDIT_USER for this call. Must be an active user on the account.
deleteNoteYesRequired note explaining the deletion (immutable audit trail).
deleteTypeYesWhy the item is being deleted (required). See list_smartlists DeleteType — typically Duplicate or Error.

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

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

Beyond destructiveHint=true, the description adds critical operational behavior: dry-run by default, confirm:true required to execute, and the immutable audit entry formed by deleteType and deleteNote. This tells the agent exactly what will happen, including the safety mechanism.

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?

Three short, front-loaded sentences. The core action is stated first, followed by legal constraints, required inputs, and the dry-run safety behavior. No filler or repetition of schema details.

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

Completeness5/5

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

For a destructive 6-parameter tool with no output schema, the description covers eligibility, required parameters, the dry-run safeguard, and the confirm switch. An agent has everything needed to invoke it safely and correctly.

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 100%, so the schema already documents all six parameters. The description adds value by clarifying that deleteType and deleteNote form an immutable audit trail and that confirm gates execution from dry-run to actual deletion.

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 opens with a specific verb and resource, 'Delete a firearm record,' and immediately differentiates this from sibling deletion tools like delete_disposition and delete_acquisition. The ATF 'Duplicate or Error' constraint further pins down exactly which records are eligible.

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 clearly states when deletion is permitted ('only for a Duplicate or Error') and explains the dry-run/confirm workflow. It does not explicitly name an alternative tool for corrections or other cases, but the eligibility constraint strongly implies the boundary.

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