Skip to main content
Glama
kondisettyravi

Bybit MCP Server

by kondisettyravi
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

get_secret_key

Retrieve API secret keys from environment variables to authenticate and secure trading operations on the Bybit cryptocurrency exchange.

Instructions

Get secret key from environment variables

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:702-710 (handler)
    Handler implementation for the 'get_secret_key' MCP tool. Returns the SECRET_KEY environment variable as text content in the standard MCP response format.
    case 'get_secret_key':
  return {
    content: [
      {
        type: 'text',
        text: process.env.SECRET_KEY || '',
      },
    ],
  };
  • src/index.ts:47-54 (registration)
    Registration of the 'get_secret_key' tool in the MCP server's ListTools handler, defining its name, description, and empty input schema (no parameters required).
    {
  name: 'get_secret_key',
  description: 'Get secret key from environment variables',
  inputSchema: {
    type: 'object',
    properties: {},
  },
},
  • src/index.ts:50-53 (schema)
    Input schema definition for the 'get_secret_key' tool: an empty object schema indicating no input parameters are 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?

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose if this requires specific permissions, has side effects, involves rate limits, or what the return format looks like, which is a significant gap for a tool accessing sensitive data.

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 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 complexity of accessing sensitive environment variables, no annotations, and no output schema, the description is incomplete. It should explain what the secret key is used for, security implications, or return format, but it only provides a basic action statement.

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 already fully documents the inputs. The description adds no parameter information, but with no parameters, a baseline of 4 is appropriate as there's nothing to compensate for.

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 ('secret key from environment variables'), making the purpose immediately understandable. It doesn't differentiate from siblings like 'get_access_key' or 'get_api_key_information', which would require specifying what type of key or from which specific environment, so it's not a perfect 5.

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 such as 'get_access_key' or 'get_api_key_information'. It lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage based on tool names 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/kondisettyravi/mcp-bybit-node'

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