Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

task_complete

Mark a Google Tasks task as completed using its account and task ID, with an optional tasklist ID that defaults to @default.

Instructions

Mark a task completed (shortcut for status='completed').

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": {
      "account": "<account>",
      "task_id": "<task_id>"
    },
    "name": "task_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes
task_idYes
tasklist_idNo@default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

B3.3/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It discloses the mutation (mark completed) but omits details on side effects, permissions, or reversibility.

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?

Single sentence, instantly clear, no waste.

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?

No output schema, no annotations, and parameter semantics are absent. The description covers only the core action, leaving many operational details unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 3 parameters with 0% description coverage. The description adds no meaning to 'account', 'task_id', or 'tasklist_id', leaving the agent without guidance on how to specify them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Mark a task completed') and resource ('task'), and distinguishes it as a shortcut for setting status to 'completed', which differentiates it from sibling tools like task_update.

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?

The description implies when to use (as a shortcut for completion) but does not explicitly provide context on when not to use or compare with alternatives like task_update.

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

Deploy Server

Other Tools