Skip to main content
Glama
Sign In
tick-mcp

tick-mcp

by KpihX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_v2_availability

Check if V2 API features are available by confirming session token configuration. Returns availability status and lists V2-only categories.

Instructions

Check whether V2 API features are available (session token configured).

[Category: Utilities]  [Auth: none]
[Related: ticktick_guide]

Returns availability status and lists all V2-only feature categories.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Describes return value (availability status and list of V2-only feature categories). No annotations provided, so description carries full burden; it sufficiently discloses behavior without side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise (3 lines) but includes metadata in brackets (category, auth, related) that could be separated. Still, it is front-loaded and each part adds value.

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 parameter-less check tool with no output schema, the description fully covers what the tool does and returns. It is complete and unambiguous.

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?

No parameters in input schema; description does not need to add parameter info. Schema coverage is 100% trivially, so baseline of 4 is appropriate.

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?

Description clearly states the tool checks V2 API availability, with the condition of session token configuration. It distinguishes from siblings like ticktick_guide by being specific to V2 availability.

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?

Indicates when to use (to check V2 availability) and mentions prerequisite (session token configured). Includes related tool hint but no explicit when-not-to-use or alternatives.

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