Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Delete pending disposition

delete_disposition
Destructive

Deletes a pending, uncommitted disposition draft; runs as a dry-run by default and requires confirm:true to execute the destructive write.

Instructions

Delete a PENDING (uncommitted) disposition draft. Dry-run by default; pass confirm:true. Destructive 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": "delete_disposition"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGUID of the pending disposition 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 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 only declare destructiveHint=true; the description adds the crucial behavioral fact that calls are dry-run by default and send nothing unless confirm:true is passed. It does not say whether an executed delete is irreversible or what the preview returns, but the dry-run default is the key non-annotation context.

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 clauses, front-loaded with the target and scope, then the safety behavior, then the risk label. No filler or repetition.

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 simple four-parameter destructive delete with no output schema and full schema documentation, the description covers the essentials: target scope, dry-run default, and destructiveness. Missing only post-delete consequences (permanence, audit effects) that would make it fully complete.

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 four parameters are already documented, including confirm's dry-run semantics and auditUser's audit-trail role. The description only restates the confirm behavior, adding no new parameter meaning, so baseline 3 applies.

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 verb and resource ('Delete a PENDING (uncommitted) disposition draft') and scopes it to uncommitted drafts, which implicitly separates it from operations on committed dispositions. It does not explicitly name a sibling, so it stops short of full differentiation.

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?

The description clearly states the dry-run default and the confirm:true escape hatch, which is strong invocation guidance. However, it never says when this tool is appropriate versus alternatives (e.g., what to do for a committed disposition, or whether commit/void tools exist), leaving usage context implied rather than stated.

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