Skip to main content
Glama

get_tasks

Retrieve all tracked tasks from Google Sheets, Gmail, and Calendar for revenue pipeline management and business coordination.

Instructions

Get all tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'get_tasks' tool. Executes by calling the shared callAPI helper with action 'getTasks', which proxies to the Google Apps Script API.
    case "get_tasks":
      result = await callAPI("getTasks");
      break;
  • index.js:280-287 (registration)
    Registration of the 'get_tasks' tool in the listTools response, including name, description, and empty input schema (no parameters required).
    {
      name: "get_tasks",
      description: "Get all tasks",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for 'get_tasks' tool: empty object, indicating no input parameters are required.
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Shared helper function callAPI used by 'get_tasks' (and other tools) to make HTTP POST requests to the Google Apps Script backend API at API_URL.
    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;
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. 'Get all tasks' implies a read operation but doesn't disclose important behavioral traits like whether this returns all tasks at once (potential performance implications), what format the tasks are returned in, whether there are permissions required, or if there are rate limits. The description provides minimal behavioral context.

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 extremely concise at just three words. It's front-loaded with the essential action and resource. There's zero wasted language or unnecessary elaboration for a simple retrieval operation.

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?

For a tool with no annotations, no output schema, and 0 parameters, the description is incomplete. While it states what the tool does, it doesn't provide enough context about what 'tasks' are in this system, what format they're returned in, or any behavioral constraints. The agent would need to guess about the return structure and system behavior.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description 'Get all tasks' appropriately indicates this is a parameterless operation that retrieves all available tasks, which aligns perfectly with the empty input schema.

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 all tasks' clearly states the verb ('Get') and resource ('tasks'), but it's vague about scope and doesn't differentiate from sibling tools like 'get_matrix_row' or 'get_metrics'. It provides basic purpose but lacks specificity about what 'all tasks' means in this context.

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 about when to use this tool versus alternatives. With many sibling tools including 'get_matrix_row', 'get_metrics', and 'get_pipeline', the description offers no context about when this specific task retrieval tool is appropriate versus other data retrieval tools.

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