Skip to main content
Glama
xuanji86

FastBound MCP

by xuanji86
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Download bound book

download_bound_book
Read-only

Generate and download the A&D bound book export for ATF compliance. Provide an audit user email to record the request and receive the file base64-encoded.

Instructions

Generate and download the A&D bound book export. Requires an auditUser email (recorded by FastBound). Returns the file base64-encoded (large exports are summarised instead). Read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNoWhich configured FastBound account to use for this one call — an alias or account number (see list_accounts). Omit to use the active account.
auditUserNoEmail recorded as X-AuditUser for the ATF audit trail. Overrides FASTBOUND_AUDIT_USER for this call. Must be an active user on the 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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint; the description adds useful behavior beyond that: the auditUser must be recorded by FastBound, output is base64-encoded, and large exports are summarised. It does not specify the summarisation threshold, but it still provides meaningful transparency.

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 front-load the core purpose, then give prerequisites and return behavior. Every clause is informative and there is no redundant filler.

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 two-parameter, no-output-schema tool, the description adequately covers purpose, prerequisites, output encoding, and an important caveat. It could still clarify what 'summarised' means and what threshold triggers it, so it is not fully complete.

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 baseline is 3. The description does not add much beyond the schema for either parameter, though it does reinforce that auditUser is tied to FastBound's audit trail.

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 names the exact resource ('A&D bound book export') and action ('Generate and download'), clearly separating it from sibling download tools like download_4473, download_attachment, and download_multiple_sale_report. It is specific and unambiguous.

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?

It states the prerequisite auditUser email and the output mode, giving an agent enough context to know when this tool is appropriate. It does not explicitly contrast it with alternatives, but the resource is unique enough that no exclusion is needed.

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