Skip to main content
Glama
Sign In
BlindPay MCP Server

BlindPay MCP Server

by blindpaylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Post Instances Transfer Quotes

PostV1InstancesTransferQuotes

Creates a transfer quote for sending stablecoins, calculating amounts and fees based on tokens, networks, and fee coverage options.

Instructions

Create Transfer Quote

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>",
      "requestBody": "<requestBody>"
    },
    "name": "PostV1InstancesTransferQuotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes
requestBodyYes
Idempotency-KeyNoOptional key to safely retry this request without performing the action twice. Retrying with the same key and an identical body replays the original response; reusing a key with a different body returns an error. Keys are kept for 24 hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.10.0
    • addedInput schema / properties / requestBody / properties / customer_token / description
      Added value: +"Token delivered to the customer wallet."
    • changedInput schema / properties / requestBody / properties / customer_token / enum
      Previous value: -[
-  "USDC",
-  "USDT",
-  "USDB"
-]New value: +[
+  "USDC",
+  "USDT",
+  "USDB",
+  "EURC",
+  "EURB"
+]
    • addedInput schema / properties / requestBody / properties / sender_token / description
      Added value: +"Token debited from the sending wallet. When it differs from customer_token the transfer converts between USDC and EURC (USDB and EURB on development instances) on Base."
    • changedInput schema / properties / requestBody / properties / sender_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 destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it does not say whether the quote locks a rate, how long it is valid, whether it moves funds ("quote" vs. actual transfer), or that it touches external networks despite openWorldHint=true. For a financial mutation classified as open-world, this is a substantial omission.

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?

Three words is not conciseness but under-specification; there is no front-loaded scope, prerequisite, or outcome statement to compress. The brevity costs information rather than saving it.

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?

The tool takes a nested request body with conversion semantics, fee fields, and a multi-chain network enum, and has no output schema to explain the response. Given that complexity, a four-word description leaves an agent unable to construct a correct call or interpret the result.

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?

Schema description coverage is only 33% at the top level, and the description compensates for none of it — instance_id, wallet_id, customer_wallet_address, customer_network, and amount_reference (whose schema description is literally an empty string) are all left to inference. The nested requestBody properties are decently documented in-schema, but the description contributes zero meaning of its own.

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?

"Create Transfer Quote" only restates the tool name and title, giving no more information than the identifier already does. With five sibling quote tools (PostV1InstancesQuotes, PostV1InstancesPayinQuotes, PostV1InstancesQuotesFx, PostV1InstancesPayinQuotesFx, PostV1InstancesTransferQuotes), the description never distinguishes what a *transfer* quote is versus a payin or FX quote.

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 call this versus the other quote endpoints, no prerequisite (e.g. wallet_id must exist), and no note on whether the returned quote must be consumed by a follow-up call such as PostV1InstancesTransfers. Nothing is misleading, but nothing is offered.

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