Skip to main content
Glama
LamboPoewert

MadeOnSol — Solana memecoin intelligence

madeonsol_coordination_alerts_get

Read-onlyIdempotent

Retrieve a specific coordination alert rule by its UUID to review its configuration and triggers.

Instructions

Get one coordination alert rule by id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRule UUID

Implementation Reference

  • Handler for madeonsol_coordination_alerts_get — executes a GET request to /kol/coordination/alerts/{id} via the restQuery helper, returning a coordination alert rule by its UUID.
    server.tool(
      "madeonsol_coordination_alerts_get",
      "Get one coordination alert rule by id.",
      { id: z.string().describe("Rule UUID") },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("GET", `/kol/coordination/alerts/${encodeURIComponent(id)}`) }],
      })
    );
  • Input schema: one required parameter 'id' (string, a Rule UUID).
    { id: z.string().describe("Rule UUID") },
  • src/index.ts:810-818 (registration)
    Registered via server.tool() within registerTools(), gated behind hasRestAuth (requires MADEONSOL_API_KEY).
    server.tool(
      "madeonsol_coordination_alerts_get",
      "Get one coordination alert rule by id.",
      { id: z.string().describe("Rule UUID") },
      { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: true },
      async ({ id }) => ({
        content: [{ type: "text" as const, text: await restQuery("GET", `/kol/coordination/alerts/${encodeURIComponent(id)}`) }],
      })
    );
  • Helper function restQuery used by the handler to make authenticated REST API calls to the MadeOnSol API v1 endpoints.
    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);
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description ('Get') is consistent but adds no additional behavioral context beyond what annotations provide.

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?

The description is a single, concise sentence that front-loads the action and resource. Every word is necessary and there is no extraneous information.

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?

For a simple get-by-id operation, the description is fairly complete given the tool's simplicity and the presence of annotations. However, it could mention what the return contains or any error conditions, which are not covered.

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 only parameter (id) is fully described in the schema as 'Rule UUID' (100% coverage). The description does not add extra meaning beyond that, but the schema already provides adequate semantics.

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 action ('Get'), the resource ('coordination alert rule'), and the scope ('one by id'). It distinguishes from sibling tools like list, create, delete, and update.

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 provides no guidance on when to use this tool versus alternatives. For example, it does not mention that this should be used when a specific rule id is known, as opposed to listing all rules.

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