Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_token_get

Read-onlyIdempotent

Retrieve a token's comprehensive snapshot: VWAP price, market cap, 24h volume, deployer reputation, KOL activity, age, and blacklist status. Optionally includes top buyer KOL wallet addresses.

Instructions

Comprehensive per-mint snapshot: price (VWAP), market cap, 24h volume, deployer reputation, KOL smart-money activity, first_seen_at + age_seconds, and blacklist status — all in one call. ULTRA adds individual KOL wallet addresses in top_buyers[].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintYesToken mint address (base58)

Implementation Reference

  • src/index.ts:656-664 (registration)
    Tool registration using server.tool() with name 'madeonsol_token_get'. Registered inside the webhook/streaming section (requires MADEONSOL_API_KEY). The schema accepts a single 'mint' parameter (base58 token address).
    server.tool(
      "madeonsol_token_get",
      "Comprehensive per-mint snapshot: price (VWAP), market cap, 24h volume, deployer reputation, KOL smart-money activity, first_seen_at + age_seconds, and blacklist status — all in one call. ULTRA adds individual KOL wallet addresses in top_buyers[].",
      { mint: z.string().describe("Token mint address (base58)") },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ mint }) => ({
        content: [{ type: "text" as const, text: await restQuery("GET", `/token/${encodeURIComponent(mint)}`) }],
      })
    );
  • Handler function for madeonsol_token_get. Takes { mint } from args and calls await restQuery('GET', `/token/${encodeURIComponent(mint)}`) to fetch a comprehensive per-mint snapshot from the MadeOnSol API. Returns the result as text content.
    async ({ mint }) => ({
      content: [{ type: "text" as const, text: await restQuery("GET", `/token/${encodeURIComponent(mint)}`) }],
    })
  • Input schema: requires a single 'mint' parameter of type string (z.string()), described as 'Token mint address (base58)'. No output schema defined (raw JSON text).
    { mint: z.string().describe("Token mint address (base58)") },
    { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
  • The restQuery helper function used by the handler. It makes an authenticated HTTP request to the MadeOnSol API (BASE_URL + /api/v1{path}) with the given method and optional body, requiring MADEONSOL_API_KEY auth mode.
    async function restQuery(method: string, path: string, body?: unknown): Promise<string> {
      const headers: Record<string, string> = {
        "Content-Type": "application/json",
        ...apiKeyHeaders(),
      };
      const res = await fetch(`${BASE_URL}/api/v1${path}`, {
        method,
        headers,
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      if (!res.ok) {
        const text = await res.text().catch(() => "");
        return `Error ${res.status}: ${text}`;
      }
      return JSON.stringify(await res.json(), null, 2);
    }
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds value by listing specific data points returned (price, market cap, volume, deployer reputation, KOL activity, blacklist status) and mentions an 'ULTRA' variant that adds wallet addresses. However, it does not explain how to access the ULTRA data or clarify if there are any rate limits or authentication requirements.

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 a single clear sentence with a bullet-like list. It is concise and front-loaded with the main purpose. However, the mention of 'ULTRA' could be clarified further without much overhead.

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?

No output schema is provided, so the description compensates by listing many return fields. It covers the essential data points for a token snapshot. However, it does not mention error cases (e.g., invalid mint address) or response format, which would be helpful for completeness.

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 input schema has 100% description coverage (the only parameter 'mint' is well-described). The description does not add any additional parameter semantics beyond what the schema provides, so a baseline score of 3 is appropriate.

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 it provides a 'Comprehensive per-mint snapshot' with specific data fields, and the verb 'get' matches the resource (token info for a mint address). It distinguishes itself from sibling tools like token_batch or token_buyer_quality by focusing on a single token snapshot.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks context about when not to use it or what other tools might be more appropriate for different use cases, such as batch queries or buyer quality analysis.

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