Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search dispositions

search_dispositions
Read-only

Search disposition records for firearms leaving inventory via sales, transfers, theft/loss, or destruction. Filter by type, serial numbers, order documents, recipient, or item. Read-only.

Instructions

Search disposition records (firearms leaving inventory: sales, FFL transfers, theft/loss, destroyed). Filter by type, TTSN/OTSN, PO/invoice/tracking, recipient contact, item. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
OTSNNo
TTSNNo
skipNoNumber of records to skip (pagination offset).
takeNoPage size (max 150).
typeNo
itemIdNo
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
externalIdNo
include4473NoInclude linked 4473 info in results.
invoiceNumberNo
itemExternalIdNo
disposedToContactIdNo
purchaseOrderNumberNo
shipmentTrackingNumberNo
isManufacturingDispositionNo
disposedToContactExternalIdNo

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

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

The description's 'Read-only' statement merely repeats the readOnlyHint annotation, and openWorldHint is not addressed. It adds no behavioral context such as pagination behavior, default result ordering, account scoping consequences, or what happens when no filters are provided, so it contributes little beyond structured metadata.

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?

Two short sentences with no filler; the action and resource lead, the domain qualifier is compact, and the filter summary plus read-only flag follow. Every sentence earns its place.

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 17-parameter search tool with no output schema, the description gives enough context to understand what is being searched and which logical filter groups exist, while skip/take/account/include4473 are covered by schema descriptions. It is slightly incomplete because it does not mention result-shaping flags like include4473 or special disposition subtypes, but it is adequate for safe invocation.

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?

With schema description coverage at only 24%, the description helps by grouping filters into meaningful categories ('TTSN/OTSN, PO/invoice/tracking, recipient contact, item'), which maps to many parameters. However, it omits semantically important parameters like isManufacturingDisposition and externalId, so it only partially compensates for the schema's low coverage.

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: 'Search disposition records', and defines the domain with the parenthetical 'firearms leaving inventory: sales, FFL transfers, theft/loss, destroyed'. This clearly separates it from search_acquisitions and other record-type search tools, even without naming a sibling.

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 description implies a broad search use case and lists filter categories, but it never states when to prefer this tool over alternatives such as get_disposition, list_disposition_items, or list_4473_dispositions. There are no explicit exclusions or when-not-to-use conditions, leaving the routing decision to inference.

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