Skip to main content
Glama
FastBound MCP

FastBound MCP

by xuanji86

Download attachment

download_attachment
Read-only

Downloads a FastBound attachment by its attachment ID, records the required audit user email for the ATF audit trail, and returns the file base64-encoded.

Instructions

Download an attachment file by its id. Requires an auditUser email (recorded by FastBound). Returns the file base64-encoded. Read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "attachmentId": "<attachmentId>"
    },
    "name": "download_attachment"
  }
}

Input 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 the account's default audit user (FASTBOUND_<ALIAS>_AUDIT_USER, else FASTBOUND_AUDIT_USER) for this call. Must be an active user on the account.
attachmentIdYesGUID of the attachment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / auditUser
      Added value: +{
      +  "description": "Email recorded as X-AuditUser for the ATF audit trail. Overrides the account's default audit user (FASTBOUND_<ALIAS>_AUDIT_USER, else FASTBOUND_AUDIT_USER) for this call. Must be an active user on the account.",
      +  "format": "email",
      +  "type": "string"
      +}
  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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds that an auditUser email is recorded by FastBound and that the file is returned base64-encoded. The statement that auditUser is 'required' is somewhat ambiguous because the schema treats it as optional with an account default, but the added return-format and audit-trail context is useful.

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?

The description is short and front-loads the main action and required identifier. The final 'Read.' sentence duplicates the readOnly annotation, and the auditUser requirement wording could be clearer.

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 read-only download tool with no output schema, the description covers the core operation, required identifier, audit context, and base64 return format. It does not explain error behavior or size limits, but those are not essential for correct invocation.

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 coverage is 100%, so the schema already documents attachmentId, auditUser, and account in detail. The description adds the audit-trail purpose of auditUser and return encoding, but its 'Requires an auditUser email' wording conflicts mildly with the schema's optional/default behavior and it does not discuss the account parameter.

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 states a specific verb and resource: 'Download an attachment file by its id.' It clearly identifies the attachment resource, distinguishing it from sibling download tools for 4473, bound book, and multiple sale reports.

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 attachment-id focus, but the description does not explicitly say when to use this tool versus other download_* siblings or when not to use it. It provides context but no exclusion or alternative-selection guidance.

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