Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search items

search_items
Read-only

Search firearm inventory using filters for serial, manufacturer, model, caliber, status, and dates. Returns a page of matching items with total count.

Instructions

Search the firearm inventory (the A&D book). Filter by serial, manufacturer, model, type, caliber, status, date ranges, TTSN/OTSN, and more. Returns a page of items plus the total record count. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mpnNo
skuNo
upcNo
otsnNo
skipNoNumber of records to skip (pagination offset).
takeNoPage size (max 150).
ttsnNoTransferee/Transferor transaction serial number.
typeNoOne or more item types (see list_smartlists ItemType).
modelNo
searchNoFree-text search across item fields.
serialNo
statusNoItem status filter, e.g. open/disposed.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
caliberNo
importerNo
locationNo
conditionNo
itemNumberNo
isDestroyedNo
isTheftLossNo
doNotDisposeNo
manufacturerNo
dispositionIdNo
hasExternalIdNo
acquisitionTypeNo
acquiredOnOrAfterNoISO date lower bound for acquisition.
disposedOnOrAfterNo
acquiredOnOrBeforeNo
disposedOnOrBeforeNo

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

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds useful behavioral detail beyond annotations by stating that the tool returns 'a page of items plus the total record count,' giving the agent a clear sense of pagination and response shape. It does not mention sorting or defaults, but the read-only annotation lowers the burden.

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 earn their place: purpose, filter capabilities, return shape, and read-only safety. The most important information is front-loaded, and there is no repetition or filler.

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 29-parameter search tool with no output schema, the description says what is searched, that it is read-only, and that it returns a page plus total count. However, it omits filter combination semantics, pagination defaults, account behavior, and what item fields appear in the response. That is a meaningful gap given the tool's complexity and the sparse schema coverage.

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 only 28%, so the description needed to compensate for many undocumented parameters. It names broad filter categories—serial, manufacturer, model, type, caliber, status, date ranges, TTSN/OTSN, and more—which is helpful high-level guidance. But it does not clarify boolean parameters, ID parameters, filter combination behavior, or the many other fields, so compensation is partial.

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?

Description clearly states a specific verb and resource: 'Search the firearm inventory (the A&D book).' It enumerates many filter dimensions, distinguishing it from sibling search tools like search_acquisitions, search_dispositions, and search_contacts. The title alone would be generic, but the description resolves the ambiguity.

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 description gives clear context: it is a read-only search over the A&D firearm inventory, so an agent can infer it is for lookup rather than mutation or acquisition/disposition searches. However, it does not explicitly name alternatives or exclusion criteria, so it stops short of the strongest possible guidance.

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