Skip to main content
Glama
Sign In
bunq Partner MCP

bunq Partner MCP

Official
by bunq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

link_document_identification

Link an uploaded attachment to a KYC document type, such as a CRYPTO_KYC_QUESTIONNAIRE, to complete identification after file upload.

Instructions

Links an uploaded attachment to a document type for KYC purposes (e.g. CRYPTO_KYC_QUESTIONNAIRE). Call after upload_attachment.

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": {
      "user_id": "<user_id>",
      "document_type": "<document_type>",
      "document_country_of_issuance": "<document_country_of_issuance>",
      "document_attachment_id": "<document_attachment_id>"
    },
    "name": "link_document_identification"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesID of the provisioned user.
document_typeYesDocument type (e.g. CRYPTO_KYC_QUESTIONNAIRE).
document_attachment_idYesID of the front attachment.
document_back_attachment_idNoID of the back attachment (optional).
document_country_of_issuanceYesISO-3166 country of issuance (use country of residence).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool performs a linking/mutation operation but does not mention idempotency, side effects, reversibility, authentication needs, or error cases. This is minimal transparency for a state-changing tool.

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?

The description is a single, front-loaded sentence that conveys purpose and a critical usage hint. Every word is necessary and there is no redundancy.

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?

The description provides the immediate context (call after upload_attachment) and mentions KYC, but does not explain what the tool returns or what to do next after linking. Given no output schema, more detail on response/behavior would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers all 5 parameters with descriptions (100% coverage). The description adds value with a concrete example for document_type and clarifies that document_country_of_issuance should be the country of residence. This goes beyond the schema's description.

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 explicitly states the action ('links an uploaded attachment to a document type for KYC purposes') and provides a concrete example ('e.g. CRYPTO_KYC_QUESTIONNAIRE'). It distinguishes itself from sibling tools like upload_attachment by specifying the sequence.

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?

The description says 'Call after upload_attachment', providing a sequencing hint but no explicit guidance on when to use vs alternatives or when not to use. Sibling tools cover different domains (e.g., banking, cards), so usage context is implied but not fully articulated.

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