Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search contacts

search_contacts
Read-only

Find individuals, organizations, and FFLs by name, FFL number, trade name, or organization name. Read-only contact search.

Instructions

Search contacts (individuals, organizations, and FFLs). Filter by name, FFL number, trade name, or organization name. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoNumber of records to skip (pagination offset).
takeNoPage size (max 150).
suffixNo
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
lastNameNo
fflNumberNo
firstNameNo
tradeNameNo
middleNameNo
licenseNameNo
organizationNameNo

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

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

The annotations already provide readOnlyHint=true, and the description repeats 'Read-only' without adding much new safety information. It does add the entity scope and filter dimensions, but omits matching semantics, pagination behavior, and the shape of the result set.

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 deliver the essential information without redundancy, putting the action and scope first. The extra filter detail follows naturally and earns its place.

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 tool with 11 parameters and no output schema, the description is minimally workable but not fully self-contained: it does not describe the return value, pagination behavior, filter combination semantics, or account selection. The read-only annotation helps, but an agent would still need to infer or probe several behaviors.

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 only 27% schema description coverage, the description's filter list is useful for grouping the many undocumented text parameters (name, FFL number, trade name, organization name). However, 'name' is ambiguous about which of firstName/lastName/middleName/suffix it means, and no exact vs partial matching semantics are stated.

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 the specific verb 'Search' with the concrete resource 'contacts', and it delineates the entity types (individuals, organizations, and FFLs). This makes it clearly distinguishable from sibling search tools such as search_items.

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 the resource name and the listed filter attributes, but the description does not name alternatives or state when to prefer get_contact over this broad search. It also does not specify whether filters are optional or whether omitting them returns all contacts.

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