Skip to main content
Glama
hrishi0102

Payman AI MCP Server

by hrishi0102

create-test-rails-payee

Generate a new payee using TEST_RAILS payment type. Specify the payee name and optional tags to streamline payment testing and tracking within the Payman AI MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the payee
tagsNoOptional tags for the payee
typeNoType of payment rails to useTEST_RAILS

Implementation Reference

  • Handler function that creates a TEST_RAILS payee by making a POST request to the Payman API, checks for API key, handles errors, and returns success or error messages.
      async ({ name, type, tags = [] }) => {
        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/payees",
            {
              method: "POST",
              headers: {
                "x-payman-api-secret": paymanApiKey,
                "Content-Type": "application/json",
              },
              body: JSON.stringify({ type, name, tags }),
            }
          );
    
          const data = await response.json();
    
          if (!response.ok) {
            return {
              content: [
                {
                  type: "text",
                  text: `Error creating payee: ${JSON.stringify(data)}`,
                },
              ],
              isError: true,
            };
          }
    
          return {
            content: [
              {
                type: "text",
                text: `TEST_RAILS payee created successfully: ${JSON.stringify(
                  data
                )}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to create payee: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
  • Zod schema defining input parameters: name (string), type (literal 'TEST_RAILS' with default), tags (optional array of strings).
      name: z.string().describe("Name of the payee"),
      type: z
        .literal("TEST_RAILS")
        .default("TEST_RAILS")
        .describe("Type of payment rails to use"),
      tags: z
        .array(z.string())
        .optional()
        .describe("Optional tags for the payee"),
    },
  • MCP server tool registration for 'create-test-rails-payee' with input schema and inline handler function.
      "create-test-rails-payee",
      {
        name: z.string().describe("Name of the payee"),
        type: z
          .literal("TEST_RAILS")
          .default("TEST_RAILS")
          .describe("Type of payment rails to use"),
        tags: z
          .array(z.string())
          .optional()
          .describe("Optional tags for the payee"),
      },
      async ({ name, type, tags = [] }) => {
        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/payees",
            {
              method: "POST",
              headers: {
                "x-payman-api-secret": paymanApiKey,
                "Content-Type": "application/json",
              },
              body: JSON.stringify({ type, name, tags }),
            }
          );
    
          const data = await response.json();
    
          if (!response.ok) {
            return {
              content: [
                {
                  type: "text",
                  text: `Error creating payee: ${JSON.stringify(data)}`,
                },
              ],
              isError: true,
            };
          }
    
          return {
            content: [
              {
                type: "text",
                text: `TEST_RAILS payee created successfully: ${JSON.stringify(
                  data
                )}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Failed to create payee: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
            isError: true,
          };
        }
      }
    );
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