Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Search acquisitions

search_acquisitions
Read-only

Find and filter acquisition records (intake events) by type, PO, invoice, tracking number, supplier contact, item, or manufacturing flag for read-only inventory lookup.

Instructions

Search acquisition records (intake events). Filter by type, PO/invoice/tracking number, supplier contact, item, and manufacturing flag. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_acquisitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
skipNoPAGE INDEX, not a record offset: 0 = first page, 1 = second page. Advance by 1 per page (never by `take`); the last page is the one with fewer than `take` records.
takeNoPage size (the server returns at most 100).
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
invoiceNumberNo
itemExternalIdNo
purchaseOrderNumberNo
acquiredFromContactIdNo
shipmentTrackingNumberNo
isManufacturingAcquisitionNo
acquiredFromContactExternalIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.2
    • changedInput schema / properties / skip / description
      Previous value: -"Number of records to skip (pagination offset)."New value: +"PAGE INDEX, not a record offset: 0 = first page, 1 = second page. Advance by 1 per page (never by `take`); the last page is the one with fewer than `take` records."
    • changedInput schema / properties / take / description
      Previous value: -"Page size (max 150)."New value: +"Page size (the server returns at most 100)."
    • changedInput schema / properties / take / maximum
      Previous value: -150New value: +100
  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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the appended 'Read-only' is essentially redundant. Beyond that, the description says nothing behavioral: it doesn't state whether filters are ANDed or ORed, whether matching is exact or partial, how many results come back, or how pagination interacts with filtering. With annotations carrying the safety profile, only minimal credit is warranted for enumerating filter categories.

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?

Two tight sentences, front-loaded with the core action and then the filter surface. No filler, though the trailing 'Read-only' is wasted given the annotations and could have been spent on a more valuable behavioral note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter, zero-required search tool with no output schema and thin schema descriptions, the definition is under-specified: return shape, result ordering, filter combination logic, and the internal/external ID distinction are all unaddressed. The schema does handle pagination well, but the description leaves the agent guessing on most of the parameter surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 21% — skip, take, and account are documented in the schema, while id, type, itemId, externalId, invoiceNumber, itemExternalId, purchaseOrderNumber, acquiredFromContactId, acquiredFromContactExternalId, shipmentTrackingNumber, and isManufacturingAcquisition are undocumented there. The description names filter categories (type, PO/invoice/tracking number, supplier contact, item, manufacturing flag) that map loosely onto those params, which is useful, but it doesn't clarify internal-ID vs external-ID pairs or match semantics, so it does not compensate for the coverage gap.

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?

The description gives a specific verb and resource ('Search acquisition records') and disambiguates the domain term with '(intake events)', so an agent knows what object is being searched. It does not distinguish itself from siblings such as get_acquisition (single-record lookup) or the search_* family, so it stops short of a 5.

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?

Usage is implied by 'Filter by ...' and 'Read-only' — the agent can infer this is a non-mutating lookup for locating records by attribute. There is no explicit when-to-use/when-not guidance, no mention of using get_acquisition for a known ID, and no statement about what happens with zero filters (return everything? error?).

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