Skip to main content
Glama

create-research-plan

Generate structured research plans for Web3 tokens by specifying token names and ticker symbols to organize crypto analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNameYesToken name
tokenTickerYesToken ticker symbol

Implementation Reference

  • The asynchronous handler function that executes the 'create-research-plan' tool logic. It logs the action, constructs a predefined research plan object with 11 sections (projectInfo, technicalFundamentals, marketStatus, listings, news, community, predictions, teamInfo, relatedCoins, socialSentiment) all set to 'planned' status, each with descriptions and sources, updates the 'researchPlan' section in storage, and returns a formatted text response containing the JSON-serialized plan.
      async ({
        tokenName,
        tokenTicker,
      }: {
        tokenName: string;
        tokenTicker: string;
      }) => {
        storage.addLogEntry(
          `Creating research plan for ${tokenName} (${tokenTicker})`
        );
    
        const researchPlan = {
          projectInfo: {
            description: "Gather basic information about the project",
            sources: ["Project website", "Documentation", "CoinMarketCap"],
            status: "planned" as const,
          },
          technicalFundamentals: {
            description: "Analyze the token's technical aspects",
            sources: ["Documentation", "GitHub", "IQ Wiki", "Token contract"],
            status: "planned" as const,
          },
          marketStatus: {
            description: "Evaluate current market performance",
            sources: ["CoinMarketCap", "TradingView", "GeckoTerminal"],
            status: "planned" as const,
          },
          listings: {
            description: "Find where the token is traded",
            sources: ["GeckoTerminal", "CoinMarketCap"],
            status: "planned" as const,
          },
          news: {
            description: "Gather recent news about the token",
            sources: ["Crypto news sites", "Twitter", "Medium"],
            status: "planned" as const,
          },
          community: {
            description: "Analyze the project's community",
            sources: ["Twitter", "Discord", "Telegram", "Reddit"],
            status: "planned" as const,
          },
          predictions: {
            description: "Collect price predictions and forecasts",
            sources: ["Analysis sites", "Expert opinions"],
            status: "planned" as const,
          },
          teamInfo: {
            description: "Research the team behind the project",
            sources: ["Project website", "LinkedIn", "Twitter"],
            status: "planned" as const,
          },
          relatedCoins: {
            description: "Identify tokens in the same category",
            sources: ["GeckoTerminal", "CoinMarketCap"],
            status: "planned" as const,
          },
          socialSentiment: {
            description: "Gauge social media sentiment",
            sources: ["Twitter", "Reddit", "Trading forums"],
            status: "planned" as const,
          },
        };
    
        storage.updateSection("researchPlan", researchPlan);
    
        return {
          content: [
            {
              type: "text",
              text: `Created research plan for ${tokenName} (${tokenTicker}):\n\n${JSON.stringify(
                researchPlan,
                null,
                2
              )}`,
            },
          ],
        };
      }
    );
  • Zod input schema for the tool: requires 'tokenName' (string, described as 'Token name') and 'tokenTicker' (string, described as 'Token ticker symbol').
    {
      tokenName: z.string().describe("Token name"),
      tokenTicker: z.string().describe("Token ticker symbol"),
    },
  • Direct registration of the 'create-research-plan' tool using server.tool(name, schema, handler) within the registerResearchTools function.
    server.tool(
      "create-research-plan",
      {
        tokenName: z.string().describe("Token name"),
        tokenTicker: z.string().describe("Token ticker symbol"),
      },
      async ({
        tokenName,
        tokenTicker,
      }: {
        tokenName: string;
        tokenTicker: string;
      }) => {
        storage.addLogEntry(
          `Creating research plan for ${tokenName} (${tokenTicker})`
        );
    
        const researchPlan = {
          projectInfo: {
            description: "Gather basic information about the project",
            sources: ["Project website", "Documentation", "CoinMarketCap"],
            status: "planned" as const,
          },
          technicalFundamentals: {
            description: "Analyze the token's technical aspects",
            sources: ["Documentation", "GitHub", "IQ Wiki", "Token contract"],
            status: "planned" as const,
          },
          marketStatus: {
            description: "Evaluate current market performance",
            sources: ["CoinMarketCap", "TradingView", "GeckoTerminal"],
            status: "planned" as const,
          },
          listings: {
            description: "Find where the token is traded",
            sources: ["GeckoTerminal", "CoinMarketCap"],
            status: "planned" as const,
          },
          news: {
            description: "Gather recent news about the token",
            sources: ["Crypto news sites", "Twitter", "Medium"],
            status: "planned" as const,
          },
          community: {
            description: "Analyze the project's community",
            sources: ["Twitter", "Discord", "Telegram", "Reddit"],
            status: "planned" as const,
          },
          predictions: {
            description: "Collect price predictions and forecasts",
            sources: ["Analysis sites", "Expert opinions"],
            status: "planned" as const,
          },
          teamInfo: {
            description: "Research the team behind the project",
            sources: ["Project website", "LinkedIn", "Twitter"],
            status: "planned" as const,
          },
          relatedCoins: {
            description: "Identify tokens in the same category",
            sources: ["GeckoTerminal", "CoinMarketCap"],
            status: "planned" as const,
          },
          socialSentiment: {
            description: "Gauge social media sentiment",
            sources: ["Twitter", "Reddit", "Trading forums"],
            status: "planned" as const,
          },
        };
    
        storage.updateSection("researchPlan", researchPlan);
    
        return {
          content: [
            {
              type: "text",
              text: `Created research plan for ${tokenName} (${tokenTicker}):\n\n${JSON.stringify(
                researchPlan,
                null,
                2
              )}`,
            },
          ],
        };
      }
    );
  • registerAllTools function that calls registerResearchTools(server, storage), thereby registering the create-research-plan tool among others.
    export function registerAllTools(
      server: McpServer,
      storage: ResearchStorage
    ): void {
      registerResearchTools(server, storage);
    }
  • src/server.ts:187-187 (registration)
    Top-level invocation of registerAllTools(server, storage) in the main server file, which ultimately registers the create-research-plan tool.
    registerAllTools(server, storage);
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/aaronjmars/web3-research-mcp'

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