Skip to main content
Glama
hrishi0102

Payman AI MCP Server

by hrishi0102

send-payment

Execute payments securely by specifying the payee ID, amount, and wallet ID. Designed for precise fund transfers using the Payman AI MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountDecimalYesAmount to send (in decimal)
payeeIdYesID of the payee to send payment to
walletIdNoThe ID of the specific wallet from which to send the funds

Implementation Reference

  • Full registration of the 'send-payment' MCP tool, including inline Zod input schema, async handler function that proxies payment requests to the Payman API, and error handling.
    server.tool(
      "send-payment",
      {
        payeeId: z.string().describe("ID of the payee to send payment to"),
        amountDecimal: z
          .number()
          .positive()
          .describe("Amount to send (in decimal)"),
        walletId: z
          .string()
          .optional()
          .describe("The ID of the specific wallet from which to send the funds"),
      },
      async ({ payeeId, amountDecimal }) => {
        if (!paymanApiKey) {
          return {
            content: [
              {
                type: "text",
                text: "API key has not been set. Please use the set-api-key tool first.",
              },
            ],
            isError: true,
          };
        }
    
        try {
          const response = await fetch(
            "https://agent.payman.ai/api/payments/send-payment",
            {
              method: "POST",
              headers: {
                "x-payman-api-secret": paymanApiKey,
                "Content-Type": "application/json",
              },
              body: JSON.stringify({ payeeId, amountDecimal }),
            }
          );
    
          const data = await response.json();
    
          if (!response.ok) {
            return {
              content: [
                {
                  type: "text",
                  text: `Error sending payment: ${JSON.stringify(data)}`,
                },
              ],
              isError: true,
            };
          }
    
          return {
            content: [
              {
                type: "text",
                text: `Payment sent successfully: ${JSON.stringify(data)}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to send payment: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • The core handler logic for the send-payment tool: validates API key presence, performs HTTP POST to external Payman API endpoint, parses response, and formats MCP-compliant success or error content.
    async ({ payeeId, amountDecimal }) => {
      if (!paymanApiKey) {
        return {
          content: [
            {
              type: "text",
              text: "API key has not been set. Please use the set-api-key tool first.",
            },
          ],
          isError: true,
        };
      }
    
      try {
        const response = await fetch(
          "https://agent.payman.ai/api/payments/send-payment",
          {
            method: "POST",
            headers: {
              "x-payman-api-secret": paymanApiKey,
              "Content-Type": "application/json",
            },
            body: JSON.stringify({ payeeId, amountDecimal }),
          }
        );
    
        const data = await response.json();
    
        if (!response.ok) {
          return {
            content: [
              {
                type: "text",
                text: `Error sending payment: ${JSON.stringify(data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            {
              type: "text",
              text: `Payment sent successfully: ${JSON.stringify(data)}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Failed to send payment: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
          isError: true,
        };
      }
    }
  • Zod input schema defining parameters for send-payment: required payeeId (string), amountDecimal (positive number), optional walletId (string).
    {
      payeeId: z.string().describe("ID of the payee to send payment to"),
      amountDecimal: z
        .number()
        .positive()
        .describe("Amount to send (in decimal)"),
      walletId: z
        .string()
        .optional()
        .describe("The ID of the specific wallet from which to send the funds"),
    },
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/hrishi0102/payman_mcp'

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