Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_discovery

Read-onlyIdempotent

List all MadeOnSol API endpoints with prices and parameter documentation. Free access, no authentication required.

Instructions

List all available MadeOnSol API endpoints with prices and parameter docs. Free, no auth required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the madeonsol_discovery tool. Fetches all available MadeOnSol API endpoints with prices and parameter docs from /api/x402 and returns them as formatted JSON. No auth required.
      async () => {
        const res = await fetch(new URL("/api/x402", BASE_URL).toString());
        const data = await res.json();
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Registration of the madeonsol_discovery tool with empty schema (no params), free/no-auth annotation, and read-only flag.
    server.tool(
      "madeonsol_discovery",
      "List all available MadeOnSol API endpoints with prices and parameter docs. Free, no auth required.",
      {},
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
  • src/index.ts:331-341 (registration)
    Full registration of the madeonsol_discovery tool using server.tool() on the McpServer. No input parameters, returns API endpoint listing.
    server.tool(
      "madeonsol_discovery",
      "List all available MadeOnSol API endpoints with prices and parameter docs. Free, no auth required.",
      {},
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
      async () => {
        const res = await fetch(new URL("/api/x402", BASE_URL).toString());
        const data = await res.json();
        return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
      }
    );
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent; description adds 'Free, no auth required' which is extra behavioral context.

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 efficient sentences, front-loaded with key information, no filler.

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 discovery tool with no parameters and no output schema, the description fully explains what the tool returns and its constraints.

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

Parameters4/5

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

No parameters exist, so schema coverage is 100%; description need not add parameter details. Baseline score of 4 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 lists all available MadeOnSol API endpoints with prices and parameter docs, which distinguishes it from specific endpoint tools like madeonsol_token_get.

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

Usage Guidelines4/5

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

The purpose is self-evident as a discovery tool, but no explicit when-not-to-use or alternative guidance is provided.

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