Skip to main content
Glama

setup_matrix_sheet

Initialize a structured Knowledge Matrix sheet with predefined headers to organize revenue tracking data for pipeline management and business operations.

Instructions

Auto-create Knowledge Matrix sheet with proper structure and headers. Run this once before using other Matrix tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'setup_matrix_sheet' tool. Dispatches the call to the Google Apps Script backend via the shared callAPI function with action 'setupMatrixSheet'.
    case "setup_matrix_sheet":
      result = await callAPI("setupMatrixSheet");
      break;
  • index.js:389-395 (registration)
    Tool registration in the ListTools response, including name, description, and empty input schema (no parameters required).
      name: "setup_matrix_sheet",
      description: "Auto-create Knowledge Matrix sheet with proper structure and headers. Run this once before using other Matrix tools.",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Input schema definition for the tool: an empty object (no input parameters).
    inputSchema: {
      type: "object",
      properties: {}
    }
  • Shared helper function callAPI that all matrix tools (including setup_matrix_sheet) use to proxy requests to the Google Apps Script backend.
    async function callAPI(action, data = {}) {
      debugLog('=== API CALL START ===');
      debugLog(`Action: ${action}`);
      debugLog(`Data: ${JSON.stringify(data)}`);
    
      try {
        // Build form-encoded body for POST
        const formData = new URLSearchParams();
        formData.append('action', action);
    
        // Add all data fields to form
        for (const [key, value] of Object.entries(data)) {
          if (value !== undefined && value !== null) {
            formData.append(key, value.toString());
          }
        }
    
        const formString = formData.toString();
        debugLog(`FormData: ${formString}`);
        debugLog(`API_URL: ${API_URL}`);
    
        // Use POST with proper content type
        const response = await fetch(API_URL, {
          method: 'POST',
          headers: {
            'Content-Type': 'application/x-www-form-urlencoded',
          },
          body: formString
        });
    
        debugLog(`Response status: ${response.status}`);
        debugLog(`Response ok: ${response.ok}`);
    
        if (!response.ok) {
          debugLog(`Response not OK: ${response.status} ${response.statusText}`);
          throw new Error(`API request failed: ${response.status} ${response.statusText}`);
        }
    
        const text = await response.text();
        debugLog(`Response text length: ${text.length}`);
        debugLog(`Response text: ${text}`);
    
        if (!text) {
          debugLog('ERROR: Empty response from API');
          throw new Error('Empty response from API');
        }
    
        const parsed = JSON.parse(text);
        debugLog(`Parsed successfully: ${JSON.stringify(parsed)}`);
        debugLog('=== API CALL END ===');
        return parsed;
    
      } catch (error) {
        debugLog(`ERROR in callAPI: ${error.message}`);
        debugLog(`ERROR stack: ${error.stack}`);
        throw error;
      }
    }
Behavior3/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. It discloses that the tool 'auto-creates' a sheet, implying a write operation, but doesn't specify behavioral traits like permissions needed, whether it overwrites existing sheets, or error handling. It adds some context about being a one-time setup, but lacks details on mutability or side effects.

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 highly concise and front-loaded: two sentences that directly state the action and usage guideline with zero waste. Every sentence earns its place by providing essential information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple setup with no parameters) and lack of annotations/output schema, the description is reasonably complete. It covers purpose and usage well, but could improve by adding more behavioral context (e.g., idempotency, output format). Without output schema, it doesn't explain return values, which is a minor gap.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate, but it implies the tool operates without inputs, aligning with the schema. Baseline is 4 for zero parameters, as it doesn't need to compensate for gaps.

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: 'Auto-create Knowledge Matrix sheet with proper structure and headers.' It specifies the verb ('auto-create'), resource ('Knowledge Matrix sheet'), and outcome ('proper structure and headers'). However, it doesn't explicitly differentiate from siblings like 'write_matrix_entry' or 'read_matrix_snapshot', which keeps it from a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidelines: 'Run this once before using other Matrix tools.' This clearly indicates when to use it (as an initial setup) and implies when not to (after setup or for other purposes), distinguishing it from alternatives like 'query_matrix' or 'write_matrix_entry'.

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/PromptishOperations/mcpSpec'

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