Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Attach disposition contact

attach_disposition_contact
Idempotent

Assign an existing recipient/buyer contact to a pending disposition, ensuring the transfer record includes the correct party.

Instructions

Assign an existing recipient/buyer contact to a pending disposition. Executes directly. Write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGUID of the pending disposition.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
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.
contactIdYesGUID of the recipient contact to attach.

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

A3.8/5.0
Behavior3/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds 'Executes directly' and 'Write', signaling immediate mutation. It does not disclose what happens if the disposition is already committed, whether a previously attached contact is replaced, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main sentence is front-loaded and precise, and the two short supplements are minimal. 'Write' is slightly redundant with 'Assign', but the overall description is tight and easy to parse.

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

Completeness3/5

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

With fully documented parameters and annotations covering safety/idempotency, the core operation is well specified. However, there is no output schema and the description omits return values, failure modes, and behavior when the disposition is not pending, leaving some ambiguity for an agent invoking the tool standalone.

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 baseline is 3 even without parameter details in the description. The phrase 'recipient/buyer' adds a small semantic clarification to contactId, but the schema already documents the core role of both parameters.

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?

Description uses a specific verb 'Assign' with a clear resource ('existing recipient/buyer contact') and target ('pending disposition'), making the operation unmistakable. It also distinguishes itself from the similar sibling attach_acquisition_contact by anchoring on dispositions.

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?

'Pending disposition' gives a clear precondition: the disposition must not yet be committed. 'Existing recipient/buyer contact' implies the contact should be created beforehand. It does not explicitly name alternatives like attach_acquisition_contact or create_contact, but the context is clear enough for selection.

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