Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get acquisition

get_acquisition
Read-only

Look up a single acquisition record by its FastBound GUID or your external ID. Read-only retrieval for quick verification.

Instructions

Retrieve a single acquisition by FastBound GUID id or your externalId. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe id value to look up.
idTypeNoWhether `id` is the FastBound GUID (default) or your externalId.
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.

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

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

The annotations already provide readOnlyHint and openWorldHint, and the description's 'Read-only' reinforces this but does not add new behavioral detail. It does not explain not-found behavior, response shape, or side effects, but for a simple read operation the annotations carry most of the burden without contradiction.

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 core purpose and identifier scope are front-loaded, and the read-only note is a single word. Every part 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?

Given the low complexity, complete parameter documentation, and read-only annotations, the description is largely sufficient for an agent to call the tool correctly. It does not describe the response object, but the name and verb make the expected return reasonably clear, and no output schema exists to clarify further.

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 the schema fully documents id, idType, and account. The description's mention of 'FastBound GUID id or your externalId' aligns with the idType enum, but it does not add meaning beyond the schema. Baseline 3 is appropriate.

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 a specific verb ('Retrieve'), a clear resource ('a single acquisition'), and identifies the two supported identifier types ('FastBound GUID id or your externalId'). This clearly distinguishes it from search-focused siblings like search_acquisitions or item-specific tools like get_acquisition_item.

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 tool is clearly positioned for fetching one acquisition by exact identifier, which implies it is not for searching or listing. It does not explicitly name alternatives or say when not to use it, but the single-record scope and identifier semantics provide adequate usage context.

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