Bybit MCP Server

get_access_key

Retrieve API access credentials from environment variables to authenticate and connect with the Bybit cryptocurrency trading platform for executing trades and managing accounts.

Instructions

Get access key from environment variables

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/index.ts:712-720 (handler)
Handler implementation for the 'get_access_key' MCP tool. Returns the ACCESS_KEY environment variable as text content.
```
case 'get_access_key':
  return {
    content: [
      {
        type: 'text',
        text: process.env.ACCESS_KEY || '',
      },
    ],
  };
```

src/index.ts:56-62 (registration)

Tool registration in the MCP server tools list, including name, description, and empty input schema.

  name: 'get_access_key',
  description: 'Get access key from environment variables',
  inputSchema: {
    type: 'object',
    properties: {},
  },
},

src/index.ts:58-61 (schema)
Input schema definition for the 'get_access_key' tool (empty object, no parameters required).
```
inputSchema: {
  type: 'object',
  properties: {},
},
```

Tool Definition Quality

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves an access key from environment variables, implying a read-only operation, but doesn't disclose behavioral traits such as error handling (e.g., if the key is missing), security implications, or what the returned value looks like. This is a significant gap for a tool with zero annotation coverage.

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 directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal. It states what the tool does but lacks completeness for effective use, such as explaining the return format, error conditions, or how it integrates with sibling tools in a trading context. This leaves gaps in understanding its role within the server.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the input. The description adds no parameter information, but since there are no parameters, a baseline of 4 is appropriate as no compensation is needed for missing 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 action ('Get') and resource ('access key'), specifying it retrieves from 'environment variables'. This distinguishes it from sibling tools like 'get_api_key_information' or 'get_secret_key' by indicating the source, though it doesn't explicitly differentiate from 'get_secret_key' which might also fetch from environment variables.

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 like 'get_api_key_information' or 'get_secret_key'. It lacks context about prerequisites (e.g., environment setup) or exclusions, leaving the agent to infer usage based on the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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/kondisettyravi/mcp-bybit-node'

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