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

google-tasks-mcp-server

by Kouta-i5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

タスクリスト取得

get-tasklist
Read-only

Retrieve task list information from Google Tasks by specifying the list ID. Use '@default' to access the default list.

Instructions

指定したタスクリストの情報を取得する。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-tasklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasklistNoタスクリストの ID。既定のリストは '@default'。ID は list-tasklists で取得できる。@default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds no additional behavioral context—no mention of what data is returned, error scenarios, or limitations. It simply restates the purpose without enriching the agent's understanding beyond the annotation.

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 extraneous content. It is concise and front-loaded, conveying the core purpose directly.

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?

For a simple read-only tool with one optional parameter and no output schema, the description is adequate but minimal. It does not mention what information is returned or provide any additional context, but given the simplicity and the schema covering the parameter, it does not feel critically incomplete.

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% for the sole parameter 'tasklist', which includes default value and how to obtain IDs. The description itself adds no parameter-specific information, so the baseline of 3 applies.

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 clearly states the action (取得 / retrieve) and the resource (タスクリスト / task list), specifying it is for a given task list. While it does not explicitly distinguish from siblings like list-tasklists, the singular 'specified' implies fetching one item, which is reasonably clear in 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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that list-tasklists should be used when the user needs an overview or that get-tasklist is for a single known list. No exclusions or context are given.

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