Skip to main content
Glama
MarveleE
by MarveleE

rap2_debug_login_info

Debug current login environment configuration for RAP2 API documentation access without exposing plaintext passwords.

Instructions

调试当前登录环境配置(不返回明文密码)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for 'rap2_debug_login_info' tool. It reads environment variables for login config using readEnvConfig(), constructs a payload with baseUrl, email, and boolean flags for session cookies and password presence (without exposing password), logs it, and returns as JSON text content.
    if (name === 'rap2_debug_login_info') {
      const { baseUrl, email, sid, sidSig } = readEnvConfig();
      const payload = { baseUrl, email, hasSid: !!sid, hasSidSig: !!sidSig, hasPassword: !!(process.env.RAP2_PASSWORD || process.env.RAP_PASSWORD) };
      logger.info({ tool: name, result: payload }, 'tool success');
      return { content: [{ type: 'text', text: JSON.stringify(payload) }] };
  • Registration of the 'rap2_debug_login_info' tool in the tools list, including name, description, and empty input schema. This list is provided to the MCP server capabilities.
    {
      name: 'rap2_debug_login_info',
      description: '调试当前登录环境配置(不返回明文密码)',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for the tool: an empty object (no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • Helper function used by the handler to read and return environment configuration variables for RAP2 login.
    function readEnvConfig() {
      const baseUrl = process.env.RAP2_BASE_URL || process.env.RAP_BASE_URL || '';
      const email = process.env.RAP2_EMAIL || process.env.RAP_EMAIL || '';
      const password = process.env.RAP2_PASSWORD || process.env.RAP_PASSWORD || '';
      const sid = process.env.RAP2_SID || '';
      const sidSig = process.env.RAP2_SID_SIG || '';
      return { baseUrl, email, password, sid, sidSig };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool debugs login environment configuration and doesn't return plaintext passwords, which is useful context about security behavior. However, it doesn't disclose other traits like whether it's read-only, requires authentication, has rate limits, or what the output format looks like. The description adds some value but leaves significant gaps.

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 clearly states the tool's purpose and a key behavioral constraint (no plaintext passwords). It's front-loaded with essential information and has zero wasted words, making it highly concise 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 has 0 parameters, no annotations, and no output schema, the description is minimally adequate. It explains what the tool does and a security constraint, but for a debugging tool, it could provide more context about what 'debug' entails (e.g., returns configuration details, error messages) or when it's useful. The lack of output schema means the description doesn't explain return values, which is a gap.

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, and schema description coverage is 100%. With no parameters to document, the baseline is 4. The description doesn't need to add parameter semantics, and it appropriately focuses on the tool's purpose without unnecessary details.

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

Purpose3/5

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

The description states the tool's purpose is to debug current login environment configuration without returning plaintext passwords. This is clear about what it does (debug configuration) but doesn't specify how it differs from sibling tools like rap2_ensure_session or rap2_test_connection, which also relate to authentication/connection. The purpose is understandable but lacks sibling differentiation.

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 it should be used (e.g., for troubleshooting login issues) or when not to use it, nor does it reference sibling tools like rap2_ensure_session or rap2_test_connection. There's implied usage for debugging, but no explicit context or exclusions.

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/MarveleE/rap2-mcp'

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