Skip to main content
Glama
Sign In
BlindPay MCP Server

BlindPay MCP Server

by blindpaylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Instances Transfers

GetV1InstancesTransfers
Read-onlyIdempotent

Retrieve and filter transfer records for a specific instance by status, token, network, customer, or wallet, with pagination controls.

Instructions

Retrieve Transfers

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": {
      "instance_id": "<instance_id>"
    },
    "name": "GetV1InstancesTransfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of items to return
tokenNoToken sent from the wallet
offsetNoNumber of items to skip
statusNo
networkNoNetwork of the sending wallet
wallet_idNo
customer_idNo
instance_idYes
ending_beforeNoA cursor for use in pagination. ending_before is an object ID that defines your place in the list.
starting_afterNoA cursor for use in pagination. starting_after is an object ID that defines your place in the list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • changedInput schema / properties / token / enum
      Previous value: -[
-  "USDC",
-  "USDT",
-  "USDB"
-]New value: +[
+  "USDC",
+  "USDT",
+  "USDB",
+  "EURC",
+  "EURB"
+]
  2. Addedv1.9.3

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context such as pagination expectations, filtering behavior, or what the list returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two words, which is concise but severely under-specified rather than appropriately sized. It is not front-loaded with useful invocation context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter listing tool with no output schema, the description is completely inadequate. It provides no information about filtering, pagination, return shape, or how it relates to sibling transfer tools.

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

Parameters2/5

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

The schema has 60% description coverage across 10 parameters, leaving status, wallet_id, customer_id, and instance_id undocumented. The description mentions none of the parameters and does not compensate for the remaining gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description merely restates the title/name: 'Retrieve Transfers' gives the resource but no list-vs-single distinction, no mention of filters, and no differentiation from siblings like GetV1InstancesTransfersById or PostV1InstancesTransfers. It is essentially a tautology rather than a specific purpose statement.

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?

There is no guidance on when to use this tool rather than GetV1InstancesTransfersById or PostV1InstancesTransfers. No prerequisites, exclusions, or alternative-selection criteria are provided.

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