Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Attach acquisition contact

attach_acquisition_contact
Idempotent

Assign an existing supplier contact to a pending acquisition to complete required contact details.

Instructions

Assign an existing supplier contact to a pending acquisition. Executes directly. Write.

Input Schema

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

A4/5.0
Behavior4/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 useful behavioral context with 'Executes directly' and 'Write', indicating immediate mutation with no confirmation step. It does not contradict the annotations, though it stops short of describing side effects like replacing an existing contact attachment.

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?

The description is extremely economical: a front-loaded purpose sentence followed by two short behavioral clauses, with no filler or redundant restatement. Every sentence contributes either to intent or execution semantics.

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?

Given the tool's simplicity, complete schema coverage, and annotations covering idempotency and safety, the description is nearly sufficient for an agent to invoke it correctly. It does not describe return values or edge cases like pre-existing contact attachments, but those are minor gaps for this 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 description coverage is 100%, with the schema already documenting id, contactId, account, and auditUser semantics. The description adds no parameter-specific detail beyond the schema, so the baseline score of 3 is appropriate.

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 the specific operation (assign), the object (existing supplier contact), and the target resource (pending acquisition), which clearly distinguishes it from sibling tools like attach_disposition_contact or set_item_acquisition_contact. The verb+resource combination leaves little ambiguity about what the tool does.

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 phrase 'existing supplier contact' and 'pending acquisition' implies when to use the tool and a boundary (do not create a contact; acquisition must not yet be committed). However, it never explicitly names alternatives such as create_contact or attach_disposition_contact, nor states when not to use it, so the guidance remains mostly implicit.

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