Skip to main content
Glama
enesjakozh
knmurphy

Glide API MCP Server

by knmurphy
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_tables

Retrieve tables for a Glide app by specifying its appId. Enables secure and type-safe data management through the Glide API MCP Server.

Instructions

Get tables for a Glide app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesID of the Glide app

Implementation Reference

  • src/index.ts:299-305 (handler)
    Handler for the 'get_tables' tool. Extracts appId from arguments, makes a GET request to `/apps/${appId}/tables` using the API client, and returns the JSON-stringified result as text content.
    case 'get_tables': {
  const { appId } = request.params.arguments as { appId: string };
  const result = await this.apiClient.makeRequest('GET', `/apps/${appId}/tables`);
  return {
    content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
  };
}
  • src/index.ts:152-165 (registration)
    Registration of the 'get_tables' tool in the ListTools response, including name, description, and input schema requiring 'appId'.
    {
  name: 'get_tables',
  description: 'Get tables for a Glide app',
  inputSchema: {
    type: 'object',
    properties: {
      appId: {
        type: 'string',
        description: 'ID of the Glide app',
      },
    },
    required: ['appId'],
  },
},
  • src/index.ts:155-164 (schema)
    Input schema definition for the 'get_tables' tool, specifying an object with required 'appId' string property.
    inputSchema: {
  type: 'object',
  properties: {
    appId: {
      type: 'string',
      description: 'ID of the Glide app',
    },
  },
  required: ['appId'],
},

Tool Definition Quality

C2.6/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 adds minimal behavioral context. It implies a read operation ('Get') but doesn't disclose traits like authentication needs, rate limits, pagination, error handling, or what 'tables' includes (e.g., structure, counts). This leaves significant gaps for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it appropriately concise. However, it lacks front-loading of critical details (e.g., scope or differentiation), slightly reducing its effectiveness despite the brevity.

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, no output schema) and lack of annotations, the description is incomplete. It doesn't explain what 'tables' entails (e.g., list of names, full metadata), return format, or error cases, leaving the agent with insufficient context for reliable use.

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 input schema fully documents the single parameter 'appId'. The description adds no additional meaning beyond implying the parameter is used to identify the Glide app, which is already clear from the schema. Baseline 3 is appropriate as the schema handles parameter documentation.

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 'Get tables for a Glide app' states a clear verb ('Get') and resource ('tables'), but it's vague about scope and granularity. It doesn't distinguish from sibling tools like 'get_table_rows' or 'get_app', leaving ambiguity about what exactly is retrieved (e.g., metadata vs. data).

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an appId), exclusions, or comparisons to siblings like 'get_table_rows' (for row data) or 'get_app' (for app details), leaving the agent to infer usage context.

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