Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

calendar_task_list_delete

Deletes a Google Tasks list and all its tasks; excludes the default list and requires confirm=true.

Instructions

Delete a Google Tasks list and all its tasks (the default list cannot be deleted).

Requires confirm=true (outward-facing or destructive).

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": {
      "list": "<list>"
    },
    "name": "calendar_task_list_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
listYesList name.
confirmNoMust be true: this action is outward-facing or destructive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses that the operation is destructive and cascading (all tasks in the list go with it), that the default list is protected, and that confirm=true is required. It stops short of stating irreversibility or permission requirements.

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?

Two sentences, no filler, with the destructive scope front-loaded and the constraint and confirmation requirement following. Nothing to cut.

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?

For a 2-parameter destructive tool with no annotations and no output schema, the description covers the essentials: cascade effect, protected target, and the confirm gate. It omits failure behavior and whether 'list' is matched by name or ID, which are minor residual gaps.

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?

Schema coverage is 100%, so the schema already documents both parameters; the description mainly restates the confirm=true requirement. It does add genuine semantics for 'list' by declaring which list values are invalid (the default list), which the schema's bare 'List name.' does not convey.

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?

States a specific verb and resource: delete a Google Tasks *list*, plus the cascade scope ('and all its tasks'). That scope distinguishes it from the sibling calendar_task_delete (which deletes a task), though the sibling is never named explicitly.

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 parenthetical '(the default list cannot be deleted)' gives one concrete when-not condition, which is real guidance. But there is no routing to alternatives (calendar_task_delete for single tasks, calendar_task_lists to inspect lists first), so the agent must infer the rest.

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