Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Undispose item

undispose_item
Destructive

Reverse a firearm disposition to return the disposed item to available inventory. Runs as a dry-run preview by default; set confirm:true to apply the change.

Instructions

Reverse a disposition: return a disposed firearm to available inventory. Dry-run by default; pass confirm:true to apply. 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": {
      "id": "<id>"
    },
    "name": "undispose_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesFastBound GUID of the disposed item.
noteNoReason for undisposing.
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 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.

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

A3.8/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, so the mutation profile is already signalled; the description reinforces it with 'Write.' and adds the material behavior that the default path is a dry run returning a preview that sends nothing. That preview-default detail is the kind of thing annotations cannot express and would change how an agent calls the tool. It does not mention audit-trail side effects or irreversibility of the reversal, keeping it from a 5.

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 sentences, front-loaded with the effect, then the safety default, then a one-word mutation marker. Nothing is wasted and the most decision-relevant fact (reversible write, dry-run first) comes early.

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 single-record mutation with a destructive hint and no output schema, the definition covers the effect, the write nature, and the safe invocation path, which is most of what an agent needs. It leaves unstated what the dry-run preview contains and whether undisposing can fail on items not currently disposed, minor gaps for this complexity.

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 description coverage is 100%, so all five parameters including confirm, auditUser and account are already documented in the schema. The description restates the confirm semantics ('Dry-run by default; pass confirm:true to apply') but adds nothing about id, note, account or auditUser. Baseline 3 applies when the schema already carries the parameter burden.

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?

The description names a specific verb and effect: 'Reverse a disposition: return a disposed firearm to available inventory.' That is far more informative than the title 'Undispose item'. It does not, however, distinguish this from nearby siblings such as delete_disposition or dispose, so it stops short of a 5.

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?

It gives operational guidance on how to run the call safely (dry-run by default, pass confirm:true to apply), which is genuinely useful. It offers no guidance on when to choose this over an alternative such as delete_disposition, nor any precondition like 'the item must currently be in a disposed state'.

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