Skip to main content
Glama
yanboishere

Infini Payment MCP Server

by yanboishere

get_payment_order

Retrieve cryptocurrency payment order details by order ID to manage USDC/USDT transactions and verify payment status.

Instructions

Get payment order details by order ID.

Args:
    order_id: The order ID to query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'get_payment_order' MCP tool. It takes an order_id parameter, makes a GET request to the Infini API /order endpoint, and returns the result as a string. Registered automatically via the @mcp.tool() decorator.
    @mcp.tool()
    def get_payment_order(order_id: str) -> str:
        """
        Get payment order details by order ID.
        
        Args:
            order_id: The order ID to query
        """
        params = {"order_id": order_id}
        result = client.request("GET", "/order", params=params)
        return str(result)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a read operation ('Get') but doesn't mention authentication requirements, rate limits, error conditions, or what happens with invalid order IDs. The description lacks critical behavioral context needed for safe and effective tool invocation.

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?

The description is appropriately concise with two sentences that directly address purpose and parameters. The 'Args:' section is structured but could be more integrated. While efficient, the second sentence could be merged with the first for better flow without losing clarity.

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?

Given the tool's low complexity (single parameter, no nested objects) and the presence of an output schema, the description is minimally adequate. However, with no annotations and incomplete parameter documentation, it leaves gaps in understanding behavioral traits and error handling. The output schema likely covers return values, but the description doesn't reference this or provide usage context.

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?

The description adds minimal parameter semantics beyond what the input schema provides. It explains that 'order_id' is 'The order ID to query,' which clarifies the parameter's purpose but doesn't specify format, validation rules, or examples. With 0% schema description coverage and only one parameter, this provides basic context but doesn't fully compensate for the schema's lack of descriptions.

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?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('payment order details'), making it immediately understandable. It distinguishes from siblings like 'list_payment_orders' by specifying retrieval by order ID rather than listing multiple orders. However, it doesn't explicitly differentiate from other read operations like 'verify_webhook_signature' beyond the resource focus.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'get_payment_order' over 'list_payment_orders' for retrieving order information, nor does it specify prerequisites like needing a valid order ID. Usage is implied by the parameter name but not explicitly stated.

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/yanboishere/infini-mcp'

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