Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete acquisition item

delete_acquisition_item
Destructive

Remove an item from a pending acquisition before finalization. Preview by default with a dry run; set confirm:true to execute the deletion.

Instructions

Remove an item from a pending acquisition. Dry-run by default; pass confirm:true. Destructive write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGUID of the acquisition.
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.
acquisitionItemIdYesGUID of the acquisition item to remove.

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

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

The description explicitly discloses the destructive nature ('Destructive write') and the safety mechanism: 'Dry-run by default; pass confirm:true.' This goes beyond the annotation by revealing the gated execution model, which is critical for an agent to invoke safely.

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?

Two short sentences, zero filler. The purpose is front-loaded, followed immediately by the most operationally important caveat (dry-run/confirm). Every word earns its place.

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 destructive tool, the description adequately conveys scope, safety guard, and execution requirement. It doesn't describe return behavior or failure cases, but the schema handles the dry-run preview detail and no output schema is expected for a delete operation.

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 100%, so the schema already documents all five parameters, including the confirm behavior. The description repeats the confirm guard but adds no new parameter meaning beyond what the property descriptions already provide.

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 precise verb and resource: 'Remove an item from a pending acquisition.' This clearly distinguishes it from siblings like delete_acquisition (whole acquisition) and delete_item (general item), and the scope is unambiguous.

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 wording 'from a pending acquisition' provides clear context for when to use this tool, implicitly excluding committed acquisitions and whole-acquisition deletion. It does not explicitly name alternative tools or exclusions, so it falls just short of a perfect score.

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