Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Bulk verify inventory

bulk_verify_inventory
Idempotent

Mark multiple serial numbers as physically verified in a cycle count and optionally update their location, with rollback support when a serial fails.

Instructions

Mark a list of serial numbers as physically verified during a cycle count, optionally updating their location. Write.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serials": "<serials>"
    },
    "name": "bulk_verify_inventory"
  }
}

Input 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.
serialsYesSerial numbers to verify.
locationNoLocation to set when updateLocation is true.
auditUserNoEmail recorded as X-AuditUser for the ATF audit trail. Overrides the account's default audit user (FASTBOUND_<ALIAS>_AUDIT_USER, else FASTBOUND_AUDIT_USER) for this call. Must be an active user on the account.
verifiedUtcNoVerification timestamp (ISO UTC); defaults to now.
updateLocationNoIf true, set the location of verified items.
rollbackPartialNoIf true, roll back all changes when any serial fails.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / auditUser / description
      Previous value: -"Email recorded as X-AuditUser for the ATF audit trail. Overrides FASTBOUND_AUDIT_USER for this call. Must be an active user on the account."New value: +"Email recorded as X-AuditUser for the ATF audit trail. Overrides the account's default audit user (FASTBOUND_<ALIAS>_AUDIT_USER, else FASTBOUND_AUDIT_USER) for this call. Must be an active user on the account."
  2. 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"
      +}
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the trailing 'Write.' adds little beyond confirming mutation. The description does add domain framing (physical verification during a cycle count) but is silent on the partial-failure default, the audit-trail side effect, and what happens when a serial is unknown — details that live only in the schema.

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?

A single front-loaded sentence carries the core action and scope, followed by a one-word mutation flag. Nothing is padded, though the bare 'Write.' is redundant against the annotations and slightly clipped in tone.

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 7-parameter bulk mutation with no output schema, the description covers the action and the optional location update but not the default failure semantics (whether a bad serial aborts the batch), the return shape, or the audit-user implication. Rich schema coverage compensates partially, leaving it adequate but not complete.

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 account, auditUser, verifiedUtc, updateLocation and rollbackPartial are all documented in the schema itself. The description only echoes the location/updateLocation coupling ('optionally updating their location') and adds no syntax, defaults, or constraints beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Mark a list of serial numbers as physically verified', plus the scope ('bulk', 'cycle count') and the optional side effect on location. It is clear what the tool does, though it never names a sibling (e.g. get_item or a single-item verify path) to sharpen the boundary.

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 'during a cycle count' implies the operating context, so an agent can infer when this applies. There is no explicit when-not guidance, no statement about what to do with serials that don't exist, and no named alternative for single-item or non-cycle-count verification.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.