Skip to main content
Glama

greptile_env_check

Verify environment variable configuration and setup status to ensure proper system operation.

Instructions

Check environment variable configuration and setup status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the greptile_env_check tool logic. It generates a report on environment variable status, API connectivity, and provides setup guidance.
    /**
     * Handle greptile_env_check tool
     */
    private async handleEnvironmentCheck(): Promise<{
      content: Array<{ type: string; text: string }>;
    }> {
      const status = this.envStatus;
    
      const report = {
        status: status.isFullyConfigured ? 'CONFIGURED' : 'INCOMPLETE',
        environment_variables: {
          GREPTILE_API_KEY: status.hasGreptileApiKey ? 'SET' : 'MISSING',
          GITHUB_TOKEN: status.hasGithubToken ? 'SET' : 'MISSING',
        },
        api_connectivity: null as string | null,
        missing_variables: status.missingVars,
        setup_instructions: status.suggestions,
      };
    
      if (this.greptileClient) {
        try {
          const healthCheck = await this.greptileClient.healthCheck();
          report.api_connectivity = healthCheck ? 'CONNECTED' : 'FAILED';
        } catch (error) {
          report.api_connectivity = 'ERROR: ' + (error as Error).message;
        }
      } else {
        report.api_connectivity = 'NOT_INITIALIZED';
      }
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(report, null, 2),
          },
        ],
      };
    }
  • src/server.ts:228-229 (registration)
    The switch case that registers and dispatches calls to the greptile_env_check tool handler.
    case 'greptile_env_check':
      return await this.handleEnvironmentCheck();
  • The tool definition including name, description, and input schema (empty object) registered in the ListTools response.
    {
      name: 'greptile_env_check',
      description: 'Check environment variable configuration and setup status',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe how it behaves—for example, whether it's a read-only check, what output format to expect, if it has side effects, or any error conditions. This leaves significant gaps in understanding the tool's operational 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 directly states the tool's function without any wasted words. It's appropriately sized for a simple tool and front-loaded with the core purpose, 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.

Completeness3/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 adequate but has clear gaps. It explains what the tool does but lacks details on behavioral traits, usage context, or output expectations, which are important even for simple tools to ensure correct invocation.

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 the input schema has 100% description coverage (though empty). The description doesn't need to add parameter information, so it appropriately focuses on the tool's purpose. A baseline score of 4 is applied since no parameters exist, and the description doesn't attempt to explain nonexistent parameters.

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 as checking environment variable configuration and setup status, which is a specific verb+resource combination. However, it doesn't differentiate itself from sibling tools like 'get_repository_info' or 'greptile_help', which might also provide status information, so it doesn't reach the highest score.

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 any prerequisites, exclusions, or specific contexts for usage, leaving the agent to infer when this check is appropriate compared to other tools on the server.

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/sosacrazy126/greptile-mcp'

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