Skip to main content
Glama
JCF0

CG Alpha MCP

by JCF0

elfa_keyword_mentions

Read-only

Track multiple keyword mentions across crypto sources to analyze market sentiment and trending tokens within specified timeframes and chains.

Instructions

Multi-keyword mentions. Params: keywords (array|string), start, end, chain, limit, cursor, sources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsNo
startNo
endNo
chainNo
limitNo
cursorNo
sourcesNo

Implementation Reference

  • MCP tool handler for 'elfa_keyword_mentions'. Parses arguments into query parameters and delegates to the generic 'elfa_query' tool handler to fetch from '/v2/data/keyword-mentions'.
    "elfa_keyword_mentions": async (args, meta) => {
      const query = {};
      if (args && args.keywords !== undefined) query.keywords = Array.isArray(args.keywords) ? args.keywords.join(",") : String(args.keywords);
      if (args && args.start   !== undefined) query.start   = args.start;
      if (args && args.end     !== undefined) query.end     = args.end;
      if (args && args.chain   !== undefined) query.chain   = args.chain;
      if (args && args.limit   !== undefined) query.limit   = args.limit;
      if (args && args.cursor  !== undefined) query.cursor  = args.cursor;
      if (args && args.sources !== undefined) query.sources = args.sources;
      return toolHandlers["elfa_query"]({ path: "/v2/data/keyword-mentions", method: "GET", query }, meta);
    },
  • Tool schema definition for 'elfa_keyword_mentions', including input schema, description, and annotations. Used in tools/list response.
    { name:"elfa_keyword_mentions",
      description:"Multi-keyword mentions. Params: keywords (array|string), start, end, chain, limit, cursor, sources.",
      inputSchema:{ type:"object", properties:{
        keywords:{type:"array", items:{type:"string"}}, start:{type:"string"}, end:{type:"string"},
        chain:{type:"string"}, limit:{type:"number"}, cursor:{type:"string"}, sources:{type:"string"}
      }},
      annotations:{ title:"ELFA: Keyword Mentions", readOnlyHint:true, openWorldHint:true }
    },
  • Helper function 'elfaKeywordMentions' that wraps the ELFA API call to '/v2/data/keyword-mentions' using safeGet. Used in index.js debug endpoint, similar logic to MCP handler.
    export const elfaKeywordMentions = async (opts) => {
      const {
        keywords,
        accountName,
        timeWindow = '7d',
        limit = 20,
        searchType = 'or',
        cursor = null,
        reposts = false
      } = opts;
    
      const params = { limit, searchType, reposts };
      if (keywords) params.keywords = keywords;
      if (accountName) params.accountName = accountName;
    
      if ('from' in opts && 'to' in opts && opts.from != null && opts.to != null) {
        params.from = opts.from; params.to = opts.to;
      } else {
        params.timeWindow = timeWindow;
      }
      if (cursor) params.cursor = cursor;
    
      return safeGet('/v2/data/keyword-mentions', params);
    };
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation with potentially open-ended data. The description adds value by listing all parameters, which helps the agent understand the scope of filtering options (keywords, date ranges, chain, limit, cursor, sources). However, it doesn't describe behavioral aspects like pagination mechanics (cursor usage), rate limits, authentication requirements, or what 'sources' refers to.

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

Conciseness3/5

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

The description is extremely concise - just one sentence listing parameters. While efficient, it's under-specified rather than appropriately concise. It front-loads the core purpose but lacks any explanatory context. Every word earns its place, but more context would be helpful for a tool with 7 parameters and no schema descriptions.

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

Completeness3/5

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

Given 7 parameters with 0% schema coverage and no output schema, the description is incomplete. It lists parameters but doesn't explain their semantics, expected formats, or relationships. The annotations help by indicating this is a read-only, open-world operation, but the description doesn't explain what the tool returns or how results are structured. For a complex query tool, more context would be needed.

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?

With 0% schema description coverage, the description carries full burden for parameter documentation. It lists all 7 parameters by name, which provides basic semantic information about what can be controlled. However, it doesn't explain what each parameter means (e.g., what 'chain' represents, what format 'start' and 'end' should use, what 'sources' options are available). The description compensates somewhat but doesn't fully explain parameter purposes.

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

Purpose3/5

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

The description states 'Multi-keyword mentions' which indicates the tool deals with keyword mentions, but it's vague about what resource or system this operates on. It doesn't specify whether this searches documents, social media, news articles, or another data source. The title annotation 'ELFA: Keyword Mentions' provides some context, but the description itself lacks specificity about the domain or target resource.

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. With sibling tools like 'elfa_query', 'elfa_token_news', and 'elfa_trending_tokens' that might also involve keyword-related operations, there's no indication of how this tool differs or when it's the appropriate choice. No prerequisites, exclusions, or comparison to alternatives are mentioned.

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/JCF0/cg-alpha-mcp'

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