Skip to main content
Glama
LawrenceCirillo

QuickBase MCP Server

quickbase_get_reports

Retrieve all reports associated with a specific table in QuickBase using the MCP server, enabling efficient data management and analysis. Input the table ID to access relevant reports.

Instructions

Get all reports for a table

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableIdYesTable ID

Implementation Reference

  • Core implementation of quickbase_get_reports: fetches reports for a given tableId via QuickBase API /reports endpoint.
    async getReports(tableId: string): Promise<any[]> {
      const response = await this.axios.get('/reports', {
        params: { tableId }
      });
      return response.data;
    }
  • MCP server dispatch handler for quickbase_get_reports tool, validates args and delegates to QuickBaseClient.getReports.
    case 'quickbase_get_reports':
      if (!args || typeof args !== 'object') {
        throw new Error('Invalid arguments');
      }
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await this.qbClient.getReports(args.tableId as string), null, 2),
          },
        ],
      };
  • Tool registration in quickbaseTools array, including name, description, and input schema for MCP server.
      name: 'quickbase_get_reports',
      description: 'Get all reports for a table',
      inputSchema: {
        type: 'object',
        properties: {
          tableId: { type: 'string', description: 'Table ID' }
        },
        required: ['tableId']
      }
    },
  • JSON schema definition for quickbase_get_reports input parameters (tableId required).
      type: 'object',
      properties: {
        tableId: { type: 'string', description: 'Table ID' }
      },
      required: ['tableId']
    }
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 it 'gets' reports, implying a read-only operation, but doesn't specify if it requires authentication, returns paginated results, includes error handling, or what format the reports are in (e.g., list of names, full details). This is a significant gap 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 that front-loads the core purpose without unnecessary words. Every part earns its place, 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 lack of annotations and output schema, the description is incomplete. It doesn't address key behavioral aspects like authentication needs, rate limits, or return format, which are crucial for an AI agent to use the tool effectively in a real-world context.

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 schema description coverage is 100%, with the single parameter 'tableId' clearly documented in the schema. The description adds no additional meaning beyond implying the table is the source for reports, which is already inferred from the schema. Baseline 3 is appropriate as the 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 ('Get') and resource ('all reports for a table'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'quickbase_run_report' or 'quickbase_get_table_info', which also involve reports or table metadata, so it lacks specific distinction.

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. For example, it doesn't explain how this differs from 'quickbase_run_report' (which likely executes a report) or 'quickbase_get_table_info' (which might include report metadata), leaving the agent to guess based on 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/LawrenceCirillo/QuickBase-MCP-Server'

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