Skip to main content
Glama
Sign In
Alcove

Alcove

Official
by OctopusGarage
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

alcove_task_add

Add a new personal task with title and optional priority, due date, notes, and tags. Organize tasks by workspace or home.

Instructions

Create a personal task.

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": {
      "title": "<title>"
    },
    "name": "alcove_task_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNo
homeNo
tagsNo
notesNo
titleYes
priorityNomedium
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states the action without mentioning side effects, permissions, or constraints. For example, it doesn't indicate if task creation is idempotent or requires authentication.

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

Conciseness3/5

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

The description is extremely concise (one sentence), but this brevity comes at the cost of completeness. While it is front-loaded, it fails to provide necessary details for effective tool selection and invocation.

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

Completeness2/5

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

Given the tool's 7 parameters and lack of annotations or schema descriptions, the description is insufficient. It does not explain return values (despite an output schema existing), parameter roles, or usage context, leaving agents underinformed.

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?

With 0% schema description coverage and no parameter explanations in the description, the meaning of the 7 parameters (e.g., 'due', 'home', 'tags') is left entirely to the schema's basic type information. The description adds no semantic value.

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 'Create a personal task.' clearly states the verb ('Create') and the resource ('personal task'), distinguishing it from sibling tools like alcove_task_cancel and alcove_task_list. It lacks further detail on what constitutes a 'personal task,' but it is unambiguous.

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. Sibling tools include task-related operations (cancel, complete, list) and alcove_inbox_todo, which may also create tasks. No context on when to choose this over others.

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