Skip to main content
Glama
JCF0

CG Alpha MCP

by JCF0

elfa_status

Read-only

Display current ELFA configuration with masked keys and .env file loading status to verify sentiment data integration for crypto market analysis.

Instructions

Show current ELFA config (key masked) and .env load info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The asynchronous handler function that executes the elfa_status tool. It returns the current ELFA base URL, environment loading info, and masked authentication details.
    "elfa_status": async () => {
      return { content: textContent({
        base: ELFA_BASE,
        loaded: ENV_INFO.loaded,
        from: ENV_INFO.from,
        vars: ENV_INFO.vars,
        auth: { headerName: ELFA_AUTH.headerName || "", scheme: ELFA_AUTH.scheme || "", key: maskKey(ELFA_AUTH.key) }
      }) };
    },
  • mcp-server.js:281-284 (registration)
    The tool registration object in the tools array, defining the name, description, empty input schema (no parameters required), and annotations.
    { name:"elfa_status",
      description:"Show current ELFA config (key masked) and .env load info.",
      inputSchema:{ type:"object", properties:{} },
      annotations:{ title:"ELFA: Status", readOnlyHint:true, openWorldHint:false }
  • The input schema for elfa_status, which is an empty object indicating no input parameters are required.
    inputSchema:{ type:"object", properties:{} },
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, indicating a safe, read-only operation with limited scope. The description adds useful context about masking keys and including .env load info, which aren't covered by annotations. However, it doesn't disclose behavioral traits like response format, error conditions, or performance characteristics.

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, efficient sentence that front-loads the core purpose ('Show current ELFA config') and adds specific details without waste. Every word earns its place, and there's no redundancy or fluff.

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 has 0 parameters, annotations covering safety (readOnlyHint) and scope (openWorldHint), but no output schema, the description is adequate but incomplete. It explains what the tool shows but not the format or structure of the output, which could be important for an agent to interpret results correctly.

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?

The input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of inputs. The description doesn't need to add parameter information, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as it avoids unnecessary details.

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 verb 'Show' and the resource 'current ELFA config' with specific details about what's included (key masked, .env load info). It distinguishes from siblings like elfa_reload_env or elfa_set_auth by focusing on status display rather than modification. However, it doesn't explicitly differentiate from all siblings (e.g., elfa_query might also show information).

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 when to use elfa_status instead of elfa_query or other siblings, nor does it specify prerequisites or exclusions. The agent must infer usage from the purpose alone.

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