Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

tasks_tasks_get

Read-only

Retrieve a specific task by its ID from a chosen task list, returning the task details needed to review or verify a to-do item.

Instructions

Get a task by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tasklist": "<tasklist>",
      "task": "<task>"
    },
    "name": "tasks_tasks_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask ID
tasklistYesTask list ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond them: no mention of failure behavior for unknown IDs, permission scope, or whether the tasklist must be owned by the caller. With annotations doing the work, this is a minimal but non-contradictory disclosure.

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?

A single front-loaded sentence with zero wasted words. It is lean to the point of being terse, but nothing extraneous is present and the core action leads.

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

Completeness3/5

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

This is a simple two-parameter read with full schema coverage and read-only annotations, so the minimal description is close to adequate. It still omits that both a task ID and a task list ID are needed together, and there is no output schema to fall back on for return-value expectations.

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%, with both 'task' and 'tasklist' documented in the schema, so the baseline is 3. The description adds no meaning beyond the schema and arguably undersells the requirement by implying a single identifier.

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 states a specific verb and resource ('Get a task'), which is clearly distinguishable from siblings like tasks_tasks_list or tasks_tasks_update. It stops short of full precision because 'by ID' understates the dual-key lookup (task plus tasklist) that the tool actually requires.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the single-record fetch versus tasks_tasks_list for enumeration, but the description never says when to prefer it or what prerequisite IDs must already be known. No exclusions or alternative routing are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.