Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Merge contacts

merge_contacts
Destructive

Merge duplicate contacts by keeping one ID and discarding the other, moving references to the winner. Runs as a dry-run preview unless you pass confirm:true to execute the destructive write.

Instructions

Merge two duplicate contacts: keep winningContactId, discard losingContactId (its references move to the winner). Dry-run by default; pass confirm:true. Destructive write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
losingContactIdYesGUID of the contact to merge away and discard.
winningContactIdYesGUID of the contact to KEEP.

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

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

The description discloses the destructive nature ('Destructive write'), the exact behavioral consequence ('references move to the winner'), and the dry-run default. This adds meaningful context beyond the destructiveHint annotation.

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 deliver the essential meaning without wasted words. The key information—what merges, what happens to references, and how to confirm—is front-loaded.

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

Completeness5/5

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

For a 5-parameter tool with no output schema, the description covers the core behavior, safety profile, and invocation guard. The account and auditUser parameters are fully documented in the schema, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds semantic value by explaining the relationship between winningContactId and losingContactId ('keep... discard... references move to the winner'). This clarifies what the merge actually does beyond the schema field names.

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?

States a specific verb and resource: 'Merge two duplicate contacts,' and immediately defines the outcome: keep winningContactId, discard losingContactId. This clearly differentiates it from sibling tools like update_contact or create_contact.

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 description identifies the use case ('duplicate contacts') and provides the critical confirmation gate ('Dry-run by default; pass confirm:true'). It does not explicitly list alternatives or exclusions, but the purpose is specific enough that an agent can select it correctly.

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