Skip to main content
Glama
knmurphy

Glide API MCP Server

by knmurphy

set_api_version

Set the Glide API version and authentication key to enable secure, type-safe interactions and manage app data or perform CRUD operations via the Glide API MCP Server.

Instructions

Set the Glide API version and authentication to use

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyYesAPI key for authentication
versionYesAPI version to use

Implementation Reference

  • Handler for the set_api_version tool. Parses arguments, validates version and apiKey, instantiates the corresponding GlideApiClient, and sets it as the active client.
    if (request.params.name === 'set_api_version' && request.params.arguments) {
      // Allow overriding environment variables with explicit settings
      const args = request.params.arguments as {
        version: 'v1' | 'v2';
        apiKey: string;
      };
    
      // Validate API key is not empty
      if (!args.apiKey.trim()) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'API key cannot be empty'
        );
      }
    
      const ClientClass = this.apiVersions[args.version];
      if (!ClientClass) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Invalid API version: ${args.version}`
        );
      }
    
      this.apiClient = new ClientClass(args.apiKey);
      
      return {
        content: [
          {
            type: 'text',
            text: `Glide API version set to ${args.version}`,
          },
        ],
      };
    }
  • Input schema for set_api_version tool, defining required 'version' (enum: 'v1'|'v2') and 'apiKey' properties.
    inputSchema: {
      type: 'object',
      properties: {
        version: {
          type: 'string',
          enum: ['v1', 'v2'],
          description: 'API version to use',
        },
        apiKey: {
          type: 'string',
          description: 'API key for authentication',
        },
      },
      required: ['version', 'apiKey'],
    },
  • src/index.ts:119-137 (registration)
    Tool registration in the ListTools handler, providing name, description, and input schema for set_api_version.
    {
      name: 'set_api_version',
      description: 'Set the Glide API version and authentication to use',
      inputSchema: {
        type: 'object',
        properties: {
          version: {
            type: 'string',
            enum: ['v1', 'v2'],
            description: 'API version to use',
          },
          apiKey: {
            type: 'string',
            description: 'API key for authentication',
          },
        },
        required: ['version', 'apiKey'],
      },
    },
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 mentions authentication but doesn't specify whether this is a one-time configuration, if it persists across sessions, what happens if invalid credentials are provided, or any rate limits. For a configuration tool with security implications, this is insufficient.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple configuration tool and front-loads the essential information.

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?

For a configuration tool with 2 parameters and 100% schema coverage, the description is minimally adequate but lacks important context. Without annotations or output schema, it should explain more about the behavioral implications (persistence, error handling) and relationship to sibling tools. The description alone doesn't provide complete operational understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema (e.g., format requirements for apiKey, implications of choosing v1 vs v2). Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Set') and the target resources ('Glide API version and authentication'), making the purpose understandable. However, it doesn't distinguish this tool from its siblings (which are all data manipulation tools), 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, nor does it mention prerequisites like needing to set API version before other operations. It simply states what the tool does without contextual usage information.

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

Related 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/knmurphy/glide-api-mcp-server'

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