Skip to main content
Glama
jun229

truemarkets-mcp-server

by jun229

Execute a prepared transfer

tm_execute_transfer
Destructive

Execute prepared transfers on True Markets to move assets between accounts. This tool finalizes transfers initiated with tm_prepare_transfer, providing transaction confirmation and details.

Instructions

Execute a transfer prepared with tm_prepare_transfer. Irreversible.

Args:

  • transfer_id (string): From tm_prepare_transfer

Returns: { success, tx_hash, chain, sent, fee, explorer_url }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transfer_idYestransfer_id from tm_prepare_transfer

Implementation Reference

  • Registration and handler implementation of the 'tm_execute_transfer' MCP tool.
      server.registerTool(
        "tm_execute_transfer",
        {
          title: "Execute a prepared transfer",
          description: `Execute a transfer prepared with tm_prepare_transfer. Irreversible.
    
    Args:
      - transfer_id (string): From tm_prepare_transfer
    
    Returns: { success, tx_hash, chain, sent, fee, explorer_url }`,
          inputSchema: {
            transfer_id: z.string().describe("transfer_id from tm_prepare_transfer"),
          },
          annotations: {
            readOnlyHint: false,
            destructiveHint: true,
            idempotentHint: false,
            openWorldHint: true,
          },
        },
        async ({ transfer_id }) => {
          // For transfers, we need to re-prepare to get payloads
          // (The prepare response payloads aren't cached like quotes)
          // This is a limitation — in production, we'd cache prepare responses too
          return {
            isError: true,
            content: [{
              type: "text",
              text: "Transfer execution requires payload signing. " +
                    "This is a scaffolded implementation — see TODO in source.",
            }],
          };
        }
      );
Behavior4/5

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

Annotations cover readOnlyHint=false, destructiveHint=true, etc., but the description adds 'Irreversible,' which is crucial behavioral context beyond annotations. It doesn't contradict annotations, as destructiveHint=true aligns with 'Irreversible.'

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 sentences with zero waste: first states purpose and key behavior, second lists returns. It's front-loaded with essential information and appropriately sized.

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?

Given the tool's complexity (irreversible, destructive), annotations provide safety info, but no output schema exists. The description lists return fields, compensating well. However, it could mention prerequisites like auth or rate limits.

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 the schema already documents the single parameter. The description adds minimal value by referencing tm_prepare_transfer, but no additional syntax or format details beyond the schema.

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 clearly states the verb ('Execute') and resource ('a prepared transfer'), specifying it's for transfers prepared with tm_prepare_transfer. It distinguishes from siblings like tm_execute_trade (trades) and tm_prepare_transfer (preparation).

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

Usage Guidelines5/5

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

It explicitly states when to use ('Execute a transfer prepared with tm_prepare_transfer') and implies when not to use (e.g., for trades, balances, or unprepared transfers). The context with sibling tools like tm_prepare_transfer provides clear alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jun229/tm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server