Skip to main content
Glama
Sign In
BlindPay MCP Server

BlindPay MCP Server

by blindpaylabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Post Instances Prepare Delegate Solana

PostV1InstancesPrepareDelegateSolana

Prepares a Solana delegation transaction for token transfers, accepting a quote ID or manual owner address, token address, and amount.

Instructions

Prepares a delegation transaction for Solana token transfers. You can either provide a quote_id (recommended) to automatically use the correct token amount and address from the quote, or manually provide owner_address, token_address, and amount.

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": "PostV1InstancesPrepareDelegateSolana"
  }
}

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. Addedv1.9.3

TDQS

B3.4/5.0
Behavior3/5

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

The word 'Prepares' usefully signals that this is a preparatory step rather than an executed transfer, adding context beyond the annotations. But with readOnlyHint=false, idempotentHint=false, and an Idempotency-Key parameter, the description says nothing about retry behavior, what is produced, or what permissions are needed.

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?

Two sentences, front-loaded with the purpose and then the selection logic. The second sentence is long but every clause maps to a real decision the caller must make.

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?

For a nested-object tool with no output schema, the description explains input modes but not what the response contains (e.g., a serialized transaction to sign) or how instance_id scopes the call. An agent would need to inspect the schema for the rest.

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?

Top-level schema coverage is only 33%, so the description carries some burden. It explains the either/or relationship between quote_id and the manual fields, which is useful, but the inner schema descriptions already state 'Required if quote_id is not provided' and that quote_id is recommended. It ignores instance_id and Idempotency-Key entirely.

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 ('Prepares') and resource ('delegation transaction for Solana token transfers'), which is enough to identify the operation. It does not explicitly differentiate itself from nearby siblings such as PostV1InstancesMintUsdbSolana or PostV1InstancesPayoutsSolana, so it stops short of a 5.

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 gives parameter-level guidance by naming quote_id as the recommended route and manual fields as the alternative. However, it offers no guidance on when to choose this tool over the other Solana-related siblings, nor any prerequisites or exclusions.

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