Skip to main content
Glama
JCF0

CG Alpha MCP

by JCF0

elfa_set_auth

Configure authentication for ELFA API by setting API key, header name, and authorization scheme to access sentiment data and trending tokens for crypto market analysis.

Instructions

Set ELFA API auth. Params: key (string), headerName (Authorization|x-elfa-api-key), scheme (e.g., Bearer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
headerNameNo
schemeNo

Implementation Reference

  • The main handler function that implements the logic for the 'elfa_set_auth' tool. It updates the global ELFA_AUTH object with the provided key, headerName, and scheme parameters, performing basic validation.
    "elfa_set_auth": async (args) => {
      const key = args && args.key;
      const headerName = args && args.headerName;
      const scheme = args && args.scheme;
      if (!key || typeof key !== "string") return { content: textContent({ ok:false, message:"Missing 'key' (string)" }), isError:true };
      if (headerName && typeof headerName === "string") ELFA_AUTH.headerName = headerName;
      if (scheme !== undefined && typeof scheme === "string") ELFA_AUTH.scheme = scheme;
      ELFA_AUTH.key = key;
      return { content: textContent({ ok:true, headerName: ELFA_AUTH.headerName || "", scheme: ELFA_AUTH.scheme || "", key: maskKey(ELFA_AUTH.key) }) };
    },
  • mcp-server.js:266-270 (registration)
    The tool registration entry in the tools array, which defines the name, description, input schema (including properties and required fields), and annotations for the 'elfa_set_auth' tool.
    { name:"elfa_set_auth",
      description:"Set ELFA API auth. Params: key (string), headerName (Authorization|x-elfa-api-key), scheme (e.g., Bearer).",
      inputSchema:{ type:"object", properties:{ key:{type:"string"}, headerName:{type:"string"}, scheme:{type:"string"} }, required:["key"] },
      annotations:{ title:"ELFA: Set Auth", readOnlyHint:false, openWorldHint:false }
    },
  • The inputSchema definition specifying the expected parameters: key (required string), headerName (string), scheme (string).
    inputSchema:{ type:"object", properties:{ key:{type:"string"}, headerName:{type:"string"}, scheme:{type:"string"} }, required:["key"] },
Behavior3/5

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

Annotations indicate readOnlyHint=false and openWorldHint=false, suggesting this is a mutation tool with closed-world behavior. The description adds value by specifying it sets API auth, implying configuration changes, but doesn't disclose details like persistence, error handling, or rate limits. No contradiction with annotations, but minimal behavioral context beyond them.

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 extremely concise and front-loaded: the first sentence states the purpose, followed by a clear parameter list with examples. Every sentence earns its place with no wasted words, making it efficient and well-structured.

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 the tool's moderate complexity (3 parameters, mutation indicated by annotations, no output schema), the description is partially complete. It covers parameters well but lacks context on how this auth setting integrates with sibling tools, return values, or error scenarios, leaving gaps for the agent.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by listing all three parameters (key, headerName, scheme) and providing semantic details: key is a string, headerName options (Authorization or x-elfa-api-key), and scheme examples (e.g., Bearer). This adds essential meaning beyond the bare schema.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Set ELFA API auth' specifies the verb ('Set') and resource ('ELFA API auth'), making it understandable. However, it doesn't differentiate from sibling tools like 'elfa_set_base' or explain how this auth setting relates to other ELFA tools, missing full sibling distinction.

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. It doesn't mention prerequisites (e.g., if auth is required before using other ELFA tools), exclusions, or context for usage, leaving the agent without clear usage instructions.

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