Skip to main content
Glama
JCF0

CG Alpha MCP

by JCF0

elfa_token_news

Read-only

Retrieve token news and sentiment data for cryptocurrency analysis. Filter by symbols, chain, time periods, and sources to monitor market trends.

Instructions

Token news. Params: symbols (comma), chain, start, end, limit, cursor, sources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsNo
chainNo
startNo
endNo
limitNo
cursorNo
sourcesNo

Implementation Reference

  • The main handler function for the MCP tool 'elfa_token_news'. It processes input arguments into query parameters and delegates the HTTP request to the generic 'elfa_query' handler targeting the ELFA '/v2/data/token-news' endpoint.
    "elfa_token_news": async (args, meta) => {
      const query = {};
      if (args && args.symbols !== undefined) query.symbols = args.symbols; // "ETH,BTC"
      if (args && args.chain   !== undefined) query.chain   = args.chain;
      if (args && args.start   !== undefined) query.start   = args.start;
      if (args && args.end     !== undefined) query.end     = args.end;
      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/token-news", method: "GET", query }, meta);
    },
  • mcp-server.js:310-317 (registration)
    The tool registration entry in the 'tools' array, which defines the name, description, input schema, and annotations for 'elfa_token_news'. This is returned by tools/list.
    { name:"elfa_token_news",
      description:"Token news. Params: symbols (comma), chain, start, end, limit, cursor, sources.",
      inputSchema:{ type:"object", properties:{
        symbols:{type:"string"}, chain:{type:"string"}, start:{type:"string"}, end:{type:"string"},
        limit:{type:"number"}, cursor:{type:"string"}, sources:{type:"string"}
      }},
      annotations:{ title:"ELFA: Token News", readOnlyHint:true, openWorldHint:true }
    },
  • A utility helper function 'elfaTokenNews' that performs a safe GET request to ELFA '/v2/data/token-news' endpoint. Used in index.js for debug endpoints, similar logic to the MCP handler.
    export const elfaTokenNews = async (opts) => {
      const { coinIds, page = 1, pageSize = 20, reposts = false } = opts;
      const params = { coinIds, page, pageSize, reposts };
      if ('from' in opts && 'to' in opts && opts.from != null && opts.to != null) {
        params.from = opts.from; params.to = opts.to;
      } else {
        params.timeWindow = opts.timeWindow || '7d';
      }
      return safeGet('/v2/data/token-news', params);
    };
Behavior3/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, which the description doesn't contradict. However, the description adds no behavioral context beyond what annotations provide—it doesn't explain what 'news' entails (e.g., real-time updates, historical data, or aggregated feeds), rate limits, or authentication needs. With annotations covering safety and scope, the description adds minimal value, scoring a baseline 3.

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

Conciseness2/5

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

The description is under-specified rather than concise—it wastes space on a tautological phrase and a bare parameter list without meaningful context. It lacks front-loaded purpose and structured details, making it inefficient for an agent to parse. While short, it doesn't earn its place with useful information, so it scores low.

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

Completeness2/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, no output schema, and annotations only covering read-only and open-world hints, the description is incomplete. It doesn't explain what 'news' returns, how parameters interact, or error conditions. For a tool with this complexity, the description fails to provide adequate context, leaving significant gaps for the agent.

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

Parameters2/5

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

The description lists parameter names ('symbols, chain, start, end, limit, cursor, sources') but provides no semantics—no explanations of what they mean, expected formats, or usage. With 0% schema description coverage and 7 parameters, this leaves all parameters undocumented. The list adds marginal value over an empty schema, but fails to compensate for the coverage gap, scoring below the baseline.

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

Purpose2/5

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

The description 'Token news' is a tautology that restates the tool name 'elfa_token_news' without specifying what the tool actually does. It doesn't provide a clear verb or resource, nor does it distinguish this tool from siblings like 'elfa_trending_tokens' or 'elfa_keyword_mentions'. The title annotation 'ELFA: Token News' adds minimal context but doesn't compensate for the description's vagueness.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, nor does it differentiate from sibling tools like 'elfa_trending_tokens' or 'elfa_query' that might handle related data. With zero usage instructions, this leaves the agent guessing about appropriate scenarios.

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