Skip to main content
Glama
yanboishere

Infini Payment MCP Server

by yanboishere

reissue_order_token

Regenerate a checkout URL token for an existing cryptocurrency payment order to restore access to payment completion.

Instructions

Reissue checkout URL token for an existing order.

Args:
    order_id: The order ID to reissue token for

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function decorated with @mcp.tool(), which registers and implements the reissue_order_token tool. It sends a POST request to the Infini API to reissue the token for the given order_id and returns the JSON response as a string.
    @mcp.tool()
    def reissue_order_token(order_id: str) -> str:
        """
        Reissue checkout URL token for an existing order.
        
        Args:
            order_id: The order ID to reissue token for
        """
        data = {"order_id": order_id}
        result = client.request("POST", "/order/token/reissue", json_data=data)
        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 the full burden of behavioral disclosure. It states the action ('Reissue') but doesn't explain what 'reissue' entails—whether it invalidates previous tokens, requires specific permissions, has rate limits, or what the new token is used for. This is a significant gap for a mutation tool with zero annotation coverage.

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 front-loaded with the core purpose in the first sentence, followed by a brief parameter explanation. It avoids unnecessary fluff, but the parameter section could be more integrated (e.g., 'Reissue checkout URL token for an existing order using its order_id'). Overall, it's efficient but not perfectly structured.

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 complexity (a mutation with one parameter) and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks critical context like behavioral traits (e.g., token invalidation, auth needs) and usage guidelines, making it incomplete for safe and effective use by an agent.

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 schema description coverage is 0%, so the description must compensate. It adds the meaning of 'order_id' ('The order ID to reissue token for'), which clarifies the parameter's role. However, it doesn't provide format details (e.g., UUID, numeric ID) or constraints, leaving some ambiguity. With one parameter and partial semantic clarification, a baseline 3 is appropriate.

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 action ('Reissue checkout URL token') and the target resource ('for an existing order'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings (like create_payment_order or get_payment_order), which would require 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 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 prerequisites (e.g., that the order must exist), when reissuing is appropriate (e.g., after token expiration), or what happens if the token is already valid. This leaves the agent with insufficient context for decision-making.

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