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

google-task-mcp

by zakikero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

google_tasks_get_authorization_url

Initiate OAuth 2.0 authorization and retrieve the URL to open in a browser for granting access to Google Tasks.

Instructions

Start local OAuth 2.0 authorization and return the URL the user must open in a browser.

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": "google_tasks_get_authorization_url"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden. It discloses that the tool starts authorization locally and produces a URL for browser opening. It doesn't clarify whether the server listens for a callback, but for a zero-parameter tool, this is adequate.

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, precise sentence that fully explains the tool's purpose and behavior without unnecessary words. It earns its place by being maximally efficient.

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 zero-parameter, simple OAuth initiation tool, the description is sufficient. It doesn't have an output schema but the return URL is implied. Some agents might benefit from knowing about timeout or error states, but the description is complete for its simplicity.

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

Parameters2/5

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

The tool has zero parameters, and schema description coverage is 100%. The description doesn't need to explain parameters, but it doesn't add any value beyond the schema. Baseline 3 is not justified because there are no parameters to enrich, and the description is minimal.

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 (start OAuth authorization) and the expected outcome (return a URL for the user to open). It distinguishes itself from sibling tools like google_tasks_complete_authorization, which handles the next step, though it doesn't explicitly name that sibling.

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

Usage Guidelines4/5

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

The description implies this is the first step in the OAuth flow, and the sibling google_tasks_complete_authorization logically follows. However, it doesn't explicitly state when not to use it or mention prerequisites like needing app credentials.

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