Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete pending acquisition

delete_acquisition
Destructive

Delete a pending acquisition draft. Use the dry-run preview to verify, then pass confirm:true to permanently remove the uncommitted record.

Instructions

Delete a PENDING (uncommitted) acquisition draft. Dry-run by default; pass confirm:true. Destructive write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGUID of the pending acquisition 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.

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?

Beyond the destructiveHint annotation, the description discloses the crucial dry-run-by-default behavior and that confirm:true is required to actually delete. This materially reduces the risk of an agent accidentally executing the destructive action.

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-load the purpose and the safety-critical execution mode. No filler or redundancy; every sentence 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 4-parameter tool with complete schema coverage and a destructiveHint annotation, the description plus schema covers the core call correctly. It is slightly incomplete on side effects (e.g., whether deleting a draft also removes its line items) and on what the dry-run preview returns, but these are not blockers to safe invocation.

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 the schema carries the full meaning of id, account, confirm, and auditUser. The description only restates confirm behavior ('pass confirm:true') already present in the schema, adding no new parameter semantics.

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?

States a specific action ('Delete') and a scoped resource ('PENDING (uncommitted) acquisition draft'), clearly separating drafts from committed acquisitions. However, it does not name or contrast any sibling tools such as delete_acquisition_item or delete_item, so differentiation is implied rather than explicit.

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?

Gives clear context (only pending/uncommitted drafts) and an explicit invocation instruction ('Dry-run by default; pass confirm:true'). It does not articulate when-not-to-use or name alternatives, so it falls short of being fully prescriptive.

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