Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set item externalId

set_item_external_id
Idempotent

Update an item's external ID to link it to your system's record, leaving all other fields unchanged.

Instructions

Set or change only the externalId of an item (links it to your system's record) without touching other fields. Write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesFastBound GUID of the item.
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.
externalIdYesYour external identifier for this item.

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.2/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 by saying it links the item to the system's record and guarantees no other fields are modified. It stops short of describing error cases or permissions, but the core behavioral profile is adequately disclosed.

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 a single sentence that front-loads the action, scope, and exclusion. Every phrase earns its place, and the final 'Write.' is acceptable, if brief, context.

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, focused write tool with 100% schema coverage and clear annotations, the description is nearly complete. It lacks an explicit mention of the response value or error behavior, but those are not required for this operation's core use.

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 schema already documents all parameters. The description adds slight extra meaning by explaining that externalId links to 'your system's record,' but it does not substantially enrich the parameter understanding beyond the schema.

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 uses a specific verb and resource: 'Set or change only the externalId of an item.' It also distinguishes itself from broader tools by explicitly stating it does so 'without touching other fields,' making its unique purpose clear.

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 phrasing 'only the externalId' and 'without touching other fields' gives clear context for when this tool is appropriate versus a broader update tool like update_item. It does not explicitly name the alternative, but the intended narrow use case is clear.

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