Skip to main content
Glama
starling-bank-mcp

starling-bank-mcp

by domdomegg

Download transaction attachment

feed_item_attachment_download
Read-only

Download a specific attachment from a transaction feed item, returning base64-encoded data for further processing.

Instructions

Download a specific attachment from a feed item (transaction). Returns the attachment as base64 encoded data.

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": {
      "accountUid": "<accountUid>",
      "categoryUid": "<categoryUid>",
      "feedItemUid": "<feedItemUid>",
      "feedItemAttachmentUid": "<feedItemAttachmentUid>"
    },
    "name": "feed_item_attachment_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountUidYesThe account UID
categoryUidYesThe category UID (use default category for main account)
feedItemUidYesThe feed item UID
feedItemAttachmentUidYesThe feed item attachment UID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the useful return detail (base64 encoded data), but discloses nothing about auth requirements, size limits, or error behavior. With annotation coverage present, a 3 is appropriate.

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 zero waste; the core action is stated first and the return format second. Nothing is padded or redundant.

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?

With no output schema, the description does carry the return-value burden and covers it via the base64 detail. Safety is covered by annotations; only auth/prerequisite context is missing, which is minor for a read-only fetch.

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 all four parameters are already documented in the schema. The description adds no syntax or format detail beyond that, making baseline 3 correct when the schema does the heavy lifting.

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?

States a specific verb (download) and resource (attachment from a feed item/transaction), so the agent immediately knows what it does. The verb 'download' inherently contrasts with the sibling feed_item_attachment_upload, though neither is explicitly named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, prerequisites, or alternatives. It neither states when to reach for this tool nor points to siblings like feed_item_attachment_upload or feed_item_get.

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