Skip to main content
Glama
enesjakozh
knmurphy

Glide API MCP Server

by knmurphy
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_app

Retrieve detailed information about a Glide app by providing its unique appId, enabling efficient management and interaction with app data using the Glide API MCP Server.

Instructions

Get information about a Glide app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesID of the Glide app

Implementation Reference

  • src/index.ts:291-297 (handler)
    Handler implementation for the 'get_app' tool. Extracts appId from arguments, calls the Glide API client's makeRequest method with GET /apps/{appId}, and returns the JSON-stringified result.
    case 'get_app': {
  const { appId } = request.params.arguments as { appId: string };
  const result = await this.apiClient.makeRequest('GET', `/apps/${appId}`);
  return {
    content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
  };
}
  • src/index.ts:138-151 (schema)
    Tool schema definition including name, description, and input schema requiring 'appId' string for the 'get_app' tool, registered in the ListTools response.
    {
  name: 'get_app',
  description: 'Get information about a Glide app',
  inputSchema: {
    type: 'object',
    properties: {
      appId: {
        type: 'string',
        description: 'ID of the Glide app',
      },
    },
    required: ['appId'],
  },
},

Tool Definition Quality

C2.7/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 of behavioral disclosure. It states the tool retrieves information (implying a read-only operation) but doesn't specify what type of information (e.g., metadata, configuration, status), whether it requires authentication, rate limits, error conditions, or response format. This leaves significant gaps for a tool with no 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 ('Get information about a Glide app') with zero waste. It's appropriately sized for a simple tool and front-loaded with the core purpose, 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 tool's simplicity (1 parameter, 100% schema coverage) but lack of annotations and output schema, the description is incomplete. It doesn't address what information is returned (e.g., app details, tables, settings), potential errors, or usage context. For a read operation with no structured output, more behavioral detail is needed to be fully helpful.

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?

The description adds no parameter semantics beyond what the input schema provides. The schema has 100% coverage with a clear description for 'appId' ('ID of the Glide app'), so the baseline is 3. The tool description doesn't explain what constitutes a valid app ID, where to find it, or examples, but the schema adequately documents the parameter.

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 ('Get information about a Glide app') with a clear verb ('Get') and resource ('Glide app'), but it's vague about what specific information is retrieved. It doesn't distinguish from siblings like 'get_tables' or 'get_table_rows', which also retrieve information from Glide apps but target different resources.

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 prerequisites (e.g., needing an app ID), exclusions, or comparisons to sibling tools like 'get_tables' (for app structure) or 'get_table_rows' (for data). Usage is implied only by the tool name and description.

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