Skip to main content
Glama
Logitale
by Logitale

toreador_get_payment_status

Get the real-time status of an ERC-20 payment session by its ID. Status values: pending, submitted, confirming, completed, expired, or failed. Includes on-chain confirmation count and transaction hash when submitted.

Instructions

Get the current status of an ERC-20 payment session by ID. Status values: pending, submitted, confirming, completed, expired, failed. Includes on-chain confirmation count and tx hash once submitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID returned by toreador_create_session.

Implementation Reference

  • Tool schema definition for toreador_get_payment_status. Declares name, description, and inputSchema requiring a single 'sessionId' string parameter.
    {
      name: "toreador_get_payment_status",
      description:
        "Get the current status of an ERC-20 payment session by ID. Status values: pending, submitted, confirming, completed, expired, failed. Includes on-chain confirmation count and tx hash once submitted.",
      inputSchema: {
        type: "object",
        properties: {
          sessionId: {
            type: "string",
            description: "Session ID returned by toreador_create_session.",
          },
        },
        required: ["sessionId"],
        additionalProperties: false,
      },
  • Tool handler for toreador_get_payment_status in the callTool dispatcher. Sends a GET request to /payment/{sessionId}/status using the toreadorRequest helper.
    case "toreador_get_payment_status":
      return toreadorRequest(
        "GET",
        `/payment/${encodeURIComponent(String(args.sessionId))}/status`,
      );
  • src/index.ts:282-282 (registration)
    Tool registration: PRO_TIER_TOOLS array is composed into ACTIVE_TOOLS only when HAS_API_KEY is true, and registered via ListToolsRequestSchema handler at line 288.
    const ACTIVE_TOOLS: Tool[] = HAS_API_KEY
  • Helper toreadorRequest: generic HTTP client that sends requests with the API key header and handles timeout/JSON parsing. Used by all tool handlers.
    async function toreadorRequest(
      method: "GET" | "POST",
      path: string,
      body?: unknown,
    ): Promise<{ ok: boolean; status: number; data: unknown }> {
      const url = `${TOREADOR_BASE_URL}${path}`;
      const headers: Record<string, string> = {
        "Accept": "application/json",
        "User-Agent": "toreador-mcp-server/0.2.0",
      };
      if (TOREADOR_API_KEY) headers["X-API-Key"] = TOREADOR_API_KEY;
      const init: RequestInit = { method, headers };
      if (body !== undefined) {
        headers["Content-Type"] = "application/json";
        init.body = JSON.stringify(body);
      }
    
      const ctrl = new AbortController();
      const timer = setTimeout(() => ctrl.abort(), REQUEST_TIMEOUT_MS);
      init.signal = ctrl.signal;
    
      try {
        const res = await fetch(url, init);
        let data: unknown = null;
        try {
          data = await res.json();
        } catch {
          // non-JSON response — leave data as null
        }
        return { ok: res.ok, status: res.status, data };
      } finally {
        clearTimeout(timer);
      }
    }
Behavior4/5

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

No annotations exist, so description bears full burden; it discloses status values and return fields, sufficient for a simple read tool.

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 concise sentences, first is front-loaded with purpose, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with full schema coverage, the description explains return values and statuses, adequate without output schema.

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 coverage is 100%, baseline 3; description adds minimal context about sessionId origin beyond 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?

Clearly states the tool retrieves payment session status by ID, lists status values and included information, distinguishing it from siblings.

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

Usage Guidelines3/5

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

Implicitly indicates use when a sessionId is available but lacks explicit guidance on when to use versus siblings or when not to.

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/Logitale/toreador-mcp-server'

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