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

google-tasks-mcp

by justerlex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

complete_task

Mark a task as completed in a specified task list using task and tasklist IDs.

Instructions

Mark a task completed (shorthand for update_task with 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": {
      "tasklist": "<tasklist>",
      "task": "<task>"
    },
    "name": "complete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask id
tasklistYesTask list id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The description discloses that the tool performs a mutation (completing a task) by referencing update_task, but does not detail side effects or authorization needs. Given no annotations, it provides reasonable transparency.

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 sentence with no redundant words, efficiently conveying the tool's purpose and relation to update_task.

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

Completeness5/5

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

For a simple tool with only two required parameters and no output schema, the description fully covers the behavior and usage context via its reference to update_task.

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?

With 100% schema description coverage, the baseline is 3. The description does not add meaning beyond the schema's minimal 'Task id' and 'Task list id' descriptions.

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 tool marks a task completed and identifies it as a shorthand for update_task with status=completed, distinguishing it from the generic update_task.

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 explicitly frames the tool as a shorthand for update_task with status=completed, guiding the agent to use complete_task for completion and update_task for other status changes.

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