Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Manage contact licenses

manage_contact_licenses

Add, update, or delete a contact's license. Provide type and number to add; use license ID to update or delete. Directly modifies license records.

Instructions

Add, update, or delete a license on a contact. For add provide type+number; for update/delete provide licenseId. Executes directly. Write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoLicense type (required). See list_smartlists LicenseType.
actionYes
numberNoLicense number (required).
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 contact.
licenseIdNoRequired for update/delete.
copyOnFileNo
expirationNoLicense expiration date (ISO).

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

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

The description says 'delete a license' and labels itself 'Write,' which implies a destructive/mutating operation, while annotations declare destructiveHint=false. Per the rubric, contradicting the annotation forces a score of 1. The additional 'Executes directly' context is useful, but the contradiction is the dominant signal.

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 pack purpose, action-specific parameter guidance, and execution behavior with no filler. The most important content is front-loaded.

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?

For a 9-parameter mutation tool with no output schema, the description captures the core action logic and immediate execution, but it omits what the call returns or how success/failure is signaled. The schema covers most parameters, yet the agent is left to guess the response shape and any side effects beyond 'Write.'

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 78%, and the description adds an actionable cross-parameter rule: type+number for add, licenseId for update/delete. This goes beyond the individual schema property descriptions by tying the action enum to specific parameter requirements.

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?

The description names the exact resource ('a license on a contact') and the full set of verbs ('Add, update, or delete'), so an agent immediately knows what the tool does. It also differentiates itself from the contact/item/acquisition/disposition siblings by focusing specifically on license management.

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?

It gives explicit conditional guidance: 'For add provide type+number; for update/delete provide licenseId.' This tells the agent which parameters to supply for each action. It does not name alternatives or exclusions, but no sibling tool directly competes with this license-management scope.

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