Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_copytrade_signals

Read-onlyIdempotent

Get recent copy-trade signals up to 7 days old from Solana KOL wallets. Filter by subscription ID, start time (ISO8601), or result limit.

Instructions

Recent fired copy-trade signals (up to 7 days). Filter by subscription_id, since (ISO8601), and limit (1–500).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_idNoFilter to one rule
sinceNoISO8601 timestamp — only signals fired at-or-after this time
limitNoMax signals to return (1–500)

Implementation Reference

  • src/index.ts:756-774 (registration)
    The tool 'madeonsol_copytrade_signals' is registered using server.tool() with schema params (subscription_id, since, limit) and a handler that calls the /api/v1/copytrade/signals endpoint via REST GET query.
    server.tool(
      "madeonsol_copytrade_signals",
      "Recent fired copy-trade signals (up to 7 days). Filter by subscription_id, since (ISO8601), and limit (1–500).",
      {
        subscription_id: z.number().optional().describe("Filter to one rule"),
        since: z.string().optional().describe("ISO8601 timestamp — only signals fired at-or-after this time"),
        limit: z.number().min(1).max(500).default(50).describe("Max signals to return (1–500)"),
      },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ subscription_id, since, limit }) => {
        const url = new URL(`${BASE_URL}/api/v1/copytrade/signals`);
        url.searchParams.set("limit", String(limit));
        if (subscription_id !== undefined) url.searchParams.set("subscription_id", String(subscription_id));
        if (since) url.searchParams.set("since", since);
        const res = await fetch(url.toString(), { headers: { "Content-Type": "application/json", ...apiKeyHeaders() } });
        const text = res.ok ? JSON.stringify(await res.json(), null, 2) : `Error ${res.status}: ${await res.text().catch(() => "")}`;
        return { content: [{ type: "text" as const, text }] };
      }
    );
  • The handler function receives { subscription_id, since, limit }, builds a URL to /api/v1/copytrade/signals with query params, fetches it with the API key headers, and returns JSON text result.
    async ({ subscription_id, since, limit }) => {
      const url = new URL(`${BASE_URL}/api/v1/copytrade/signals`);
      url.searchParams.set("limit", String(limit));
      if (subscription_id !== undefined) url.searchParams.set("subscription_id", String(subscription_id));
      if (since) url.searchParams.set("since", since);
      const res = await fetch(url.toString(), { headers: { "Content-Type": "application/json", ...apiKeyHeaders() } });
      const text = res.ok ? JSON.stringify(await res.json(), null, 2) : `Error ${res.status}: ${await res.text().catch(() => "")}`;
      return { content: [{ type: "text" as const, text }] };
    }
  • Zod schema defines optional subscription_id (number), optional since (ISO8601 string), and limit (number 1-500, default 50).
    {
      subscription_id: z.number().optional().describe("Filter to one rule"),
      since: z.string().optional().describe("ISO8601 timestamp — only signals fired at-or-after this time"),
      limit: z.number().min(1).max(500).default(50).describe("Max signals to return (1–500)"),
    },
  • src/index.ts:1066-1066 (registration)
    The tool is also listed in the Smithery server card metadata with its description.
    { name: "madeonsol_copytrade_signals", description: "Recent fired copy-trade signals (up to 7 days). PRO/ULTRA." },
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds the 7-day recency constraint and filtering options, providing useful behavioral context beyond annotations.

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 sentences, front-loaded purpose, no superfluous words. Efficiently conveys core functionality.

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

Completeness2/5

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

No output schema exists, yet the description does not explain return format (e.g., structure of signals, pagination). Leaves agents guessing about response shape, which is a significant gap.

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?

With 100% schema coverage, the baseline is 3. The description mentions 'since (ISO8601)' and 'limit (1–500)' but these details are already in the schema. No significant extra value.

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 returns 'recent fired copy-trade signals' with a specific time bound of 7 days, distinguishing it from sibling tools like copytrade_list which lists rules.

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 lists filter parameters but does not explicitly state when to use this tool versus alternatives or provide exclusions. It implies use for reading signals but lacks depth.

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/LamboPoewert/mcp-server-madeonsol'

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