Skip to main content
Glama
Logitale
by Logitale

toreador_list_sessions

List the 50 most recent ERC-20 payment sessions for your account, including status, transaction hash, confirmations, and timestamps.

Instructions

List the 50 most recent ERC-20 payment sessions for the authenticated account. Includes status, tx hash, confirmations and timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'toreador_list_sessions' dispatches an HTTP GET request to the '/sessions' endpoint via the shared toreadorRequest helper.
    case "toreador_list_sessions":
      return toreadorRequest("GET", "/sessions");
  • The schema definition for 'toreador_list_sessions' — it takes no input parameters (empty properties object).
    {
      name: "toreador_list_sessions",
      description:
        "List the 50 most recent ERC-20 payment sessions for the authenticated account. Includes status, tx hash, confirmations and timestamps.",
      inputSchema: {
        type: "object",
        properties: {},
        additionalProperties: false,
      },
    },
  • src/index.ts:288-289 (registration)
    The tool is registered via the ListToolsRequestSchema handler which returns the composed ACTIVE_TOOLS array (which includes toreador_list_sessions when a Pro API key is present).
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: ACTIVE_TOOLS }));
  • src/index.ts:282-284 (registration)
    ACTIVE_TOOLS is composed from FREE_TIER_TOOLS and PRO_TIER_TOOLS; toreador_list_sessions is part of PRO_TIER_TOOLS (line 89), so it's only registered when HAS_API_KEY is true.
    const ACTIVE_TOOLS: Tool[] = HAS_API_KEY
      ? [...FREE_TIER_TOOLS, ...PRO_TIER_TOOLS]
      : FREE_TIER_TOOLS;
  • The shared toreadorRequest helper function that all tools use to make HTTP requests to the Toreador API. 'toreador_list_sessions' calls this with GET /sessions.
    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?

With no annotations, the description carries the burden. It explicitly states 'list' (implying read-only) and lists included data fields (status, tx hash, confirmations, timestamps). It does not disclose rate limits or further behavioral traits, but for a simple read operation, this is sufficient.

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?

A single, clear sentence with no extraneous words. Every phrase adds value: '50 most recent', 'ERC-20 payment sessions', 'authenticated account', and the list of included fields.

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

Completeness4/5

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

Given the simplicity (no parameters, no output schema), the description covers the essentials. However, it does not mention pagination or how to retrieve older sessions, which could be useful context. Overall adequate but not perfect.

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

Parameters5/5

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

The input schema has zero parameters (100% coverage trivially). The description adds significant meaning by specifying the count (50 most recent) and included fields, which is valuable context beyond the empty 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?

The description clearly states the tool lists the 50 most recent ERC-20 payment sessions for the authenticated account. It specifies the resource (sessions), verb (list), and scope (50 most recent, authenticated account), distinguishing it from siblings like create_session and generate_qr.

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?

The description implies usage for viewing recent sessions but does not explicitly state when to use this tool versus alternatives like list_history. No when-not or alternative tools are mentioned, leaving room for improvement.

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