Manufact

Back to submission

kaneo-mcp

cloud.kaneo.app/api/mcp

Protocol: MCP 2026-07-28
Server version: 1.0.0
Supports: Tools

Overall score

Last reviewed at Oct 16, 2026, 15:15:57 UTC

Server metadata

3 of 8 fields30/1003 / 10 pts

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

kaneo-mcp

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 1.0.0

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools.

10/10Source

Protocol

Pass100/10020 / 20 pts

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP modern negotiation succeeded in 790ms

Source

Tools list returns results

38 tool(s) returned

Source

Resources list responds

0 resource(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues78/10023.4 / 30 pts

Tool definitions, annotations, and client compatibility.

All tools have descriptions

All tools have non-empty descriptions

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

All tools have OpenAI behavior hints

114 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

errorChatGPT

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Claude tools declare applicable behavior hints

38 Claude behavior annotation issue(s) found

How to fix: For Claude directory submission, declare the applicable annotations.readOnlyHint or annotations.destructiveHint value as a boolean on every tool.

errorClaude.ai

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Tool names use valid characters

All tool names use valid characters

Source

All tools have a display title

38 tool(s) missing a display title: whoami, list_workspaces, list_projects, get_project, create_project, update_project, list_tasks, get_task, get_task_by_ticket_id, create_task, duplicate_task, update_task, move_task, update_task_status, list_task_comments, create_task_comment, update_task_comment, delete_task_comment, list_workspace_labels, create_label, attach_label_to_task, detach_label_from_task, create_task_relation, get_task_relations, delete_task_relation, delete_label, list_workspace_members, search, list_project_columns, delete_task, update_task_assignee, update_task_due_date, list_task_time_entries, get_time_entry, create_time_entry, update_time_entry, list_task_activity, list_notifications

How to fix: Set the top-level tool.title to a short human-readable label (for example, "Search catalog"). Claude directory submission requires tool titles; annotations.title remains accepted only as a legacy fallback.

errorClaude.ai

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

ChatGPT tool names are unique

All tool names are unique

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

MCP Apps

Not applicable-Optional

App resources, metadata, and rendering requirements.

Tool invocation metadata present

No view resources found — view checks skipped

Source

View resource envelope is valid

No view resources found — view checks skipped

All discovered view resources were inspected

No view resources found — view checks skipped

Source

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

Declared domains respond

No view resources found — view checks skipped

View resource metadata complete

No view resources found — view checks skipped

Source

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

Tool documentation quality

38 tools reviewed36/10014.4 / 40 pts

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

whoamiTitles 28Descriptions 74Inputs 100Annotations 0Outputs 054/100

Title28/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description74/100

Return the current Kaneo user for the configured authentication method.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "whoami",
  "description": "Return the current Kaneo user for the configured authentication method.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  }
}

list_workspacesTitles 63Descriptions 70Inputs 100Annotations 0Outputs 062/100

Title63/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

List workspaces (Better Auth organizations) the signed-in user can access.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_workspaces",
  "description": "List workspaces (Better Auth organizations) the signed-in user can access.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  }
}

list_projectsTitles 48Descriptions 62Inputs 61Annotations 0Outputs 046/100

Title48/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description62/100

List projects in a workspace.

Describe the returned information so the agent knows whether it will answer the request.

Inputs61/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

workspaceId

Workspace ID

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

includeArchived

Include archived projects

Explain what happens when this optional value is omitted.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_projects",
  "description": "List projects in a workspace.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "workspaceId"
    ],
    "properties": {
      "workspaceId": {
        "type": "string",
        "minLength": 1,
        "description": "Workspace ID"
      },
      "includeArchived": {
        "type": "boolean",
        "description": "Include archived projects"
      }
    }
  }
}

get_projectTitles 56Descriptions 69Inputs 0Annotations 0Outputs 033/100

Title56/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description69/100

Get a single project by ID.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_project",
  "description": "Get a single project by ID.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

create_projectTitles 48Descriptions 60Inputs 0Annotations 0Outputs 029/100

Title48/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description60/100

Create a project in a workspace.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

Not provided

Missing description. Explain what this value means and how to supply it.

workspaceId

Not provided

Missing description. Explain what this value means and how to supply it.

icon

Not provided

Missing description. Explain what this value means and how to supply it.

slug

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_project",
  "description": "Create a project in a workspace.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "name",
      "workspaceId",
      "icon",
      "slug"
    ],
    "properties": {
      "icon": {
        "type": "string",
        "minLength": 1
      },
      "name": {
        "type": "string",
        "minLength": 1
      },
      "slug": {
        "type": "string",
        "minLength": 1
      },
      "workspaceId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

update_projectTitles 53Descriptions 74Inputs 0Annotations 0Outputs 034/100

Title53/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description74/100

Update project metadata (PATCH-style: only provided fields are changed).

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

name

Not provided

Missing description. Explain what this value means and how to supply it.

icon

Not provided

Missing description. Explain what this value means and how to supply it.

slug

Not provided

Missing description. Explain what this value means and how to supply it.

description

Not provided

Missing description. Explain what this value means and how to supply it.

isPublic

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_project",
  "description": "Update project metadata (PATCH-style: only provided fields are changed).",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1
      },
      "icon": {
        "type": "string"
      },
      "name": {
        "type": "string",
        "minLength": 1
      },
      "slug": {
        "type": "string",
        "minLength": 1
      },
      "isPublic": {
        "type": "boolean"
      },
      "description": {
        "type": "string"
      }
    }
  }
}

list_tasksTitles 51Descriptions 82Inputs 0Annotations 0Outputs 035/100

Title51/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description82/100

List a bounded page of tasks for a project (50 by default, maximum 100). Use pagination.totalPages and page to retrieve the rest; filters and sorting apply before pagination. For every task page, also follow relatedPage through pagination.relatedTotalPages for complete labels, links and column metadata.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 11 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

projectId

Not provided

Missing description. Explain what this value means and how to supply it.

status

Not provided

Missing description. Explain what this value means and how to supply it.

priority

Not provided

Missing description. Explain what this value means and how to supply it.

assigneeId

Not provided

Missing description. Explain what this value means and how to supply it.

page

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

sortBy

Not provided

Missing description. Explain what this value means and how to supply it.

sortOrder

Not provided

Missing description. Explain what this value means and how to supply it.

dueBefore

Not provided

Missing description. Explain what this value means and how to supply it.

dueAfter

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_tasks",
  "description": "List a bounded page of tasks for a project (50 by default, maximum 100). Use pagination.totalPages and page to retrieve the rest; filters and sorting apply before pagination. For every task page, also follow relatedPage through pagination.relatedTotalPages for complete labels, links and column metadata.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "projectId"
    ],
    "properties": {
      "page": {
        "type": "integer",
        "maximum": 1000000,
        "minimum": 1
      },
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1
      },
      "sortBy": {
        "enum": [
          "createdAt",
          "priority",
          "dueDate",
          "position",
          "title",
          "number"
        ],
        "type": "string"
      },
      "status": {
        "type": "string",
        "minLength": 1
      },
      "dueAfter": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "priority": {
        "enum": [
          "no-priority",
          "low",
          "medium",
          "high",
          "urgent"
        ],
        "type": "string"
      },
      "dueBefore": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "projectId": {
        "type": "string",
        "minLength": 1
      },
      "sortOrder": {
        "enum": [
          "asc",
          "desc"
        ],
        "type": "string"
      },
      "assigneeId": {
        "type": "string",
        "minLength": 1
      },
      "relatedPage": {
        "type": "integer",
        "maximum": 1000000,
        "minimum": 1
      }
    }
  }
}

get_taskTitles 47Descriptions 67Inputs 0Annotations 0Outputs 030/100

Title47/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description67/100

Get a task by ID.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_task",
  "description": "Get a task by ID.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

get_task_by_ticket_idTitles 51Descriptions 76Inputs 0Annotations 0Outputs 034/100

Title51/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description76/100

Get one task by its ticket ID (project key and number, e.g. KAN-12). If multiple accessible tasks share the ID, provide workspaceId or projectId.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ticketId

Not provided

Missing description. Explain what this value means and how to supply it.

workspaceId

Not provided

Missing description. Explain what this value means and how to supply it.

projectId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_task_by_ticket_id",
  "description": "Get one task by its ticket ID (project key and number, e.g. KAN-12). If multiple accessible tasks share the ID, provide workspaceId or projectId.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "ticketId"
    ],
    "properties": {
      "ticketId": {
        "type": "string",
        "minLength": 1
      },
      "projectId": {
        "type": "string",
        "minLength": 1
      },
      "workspaceId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

create_taskTitles 60Descriptions 59Inputs 0Annotations 0Outputs 032/100

Title60/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description59/100

Create a task in a project.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

projectId

Not provided

Missing description. Explain what this value means and how to supply it.

title

Not provided

Missing description. Explain what this value means and how to supply it.

description

Not provided

Missing description. Explain what this value means and how to supply it.

priority

Not provided

Missing description. Explain what this value means and how to supply it.

status

Not provided

Missing description. Explain what this value means and how to supply it.

startDate

Not provided

Missing description. Explain what this value means and how to supply it.

dueDate

Not provided

Missing description. Explain what this value means and how to supply it.

userId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_task",
  "description": "Create a task in a project.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "projectId",
      "title",
      "description",
      "priority",
      "status"
    ],
    "properties": {
      "title": {
        "type": "string",
        "minLength": 1
      },
      "status": {
        "type": "string",
        "minLength": 1
      },
      "userId": {
        "type": "string",
        "minLength": 1
      },
      "dueDate": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "priority": {
        "enum": [
          "no-priority",
          "low",
          "medium",
          "high",
          "urgent"
        ],
        "type": "string"
      },
      "projectId": {
        "type": "string",
        "minLength": 1
      },
      "startDate": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "description": {
        "type": "string"
      }
    }
  }
}

duplicate_taskTitles 54Descriptions 73Inputs 0Annotations 0Outputs 034/100

Title54/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description73/100

Duplicate a task in the same project, copying its fields and labels. Pass title to rename the copy.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

title

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "duplicate_task",
  "description": "Duplicate a task in the same project, copying its fields and labels. Pass title to rename the copy.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "title": {
        "type": "string",
        "minLength": 1
      },
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

update_taskTitles 52Descriptions 69Inputs 0Annotations 0Outputs 032/100

Title52/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description69/100

Update a task (fetches current task, merges fields, then full update).

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 10 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

title

Not provided

Missing description. Explain what this value means and how to supply it.

description

Not provided

Missing description. Explain what this value means and how to supply it.

status

Not provided

Missing description. Explain what this value means and how to supply it.

priority

Not provided

Missing description. Explain what this value means and how to supply it.

projectId

Not provided

Missing description. Explain what this value means and how to supply it.

position

Not provided

Missing description. Explain what this value means and how to supply it.

startDate

Not provided

Missing description. Explain what this value means and how to supply it.

dueDate

Not provided

Missing description. Explain what this value means and how to supply it.

userId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_task",
  "description": "Update a task (fetches current task, merges fields, then full update).",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "title": {
        "type": "string",
        "minLength": 1
      },
      "status": {
        "type": "string",
        "minLength": 1
      },
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "userId": {
        "anyOf": [
          {
            "type": "string",
            "minLength": 1
          },
          {
            "type": "null"
          }
        ]
      },
      "dueDate": {
        "anyOf": [
          {
            "type": "string",
            "format": "date-time",
            "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
          },
          {
            "type": "null"
          }
        ]
      },
      "position": {
        "type": "number"
      },
      "priority": {
        "enum": [
          "no-priority",
          "low",
          "medium",
          "high",
          "urgent"
        ],
        "type": "string"
      },
      "projectId": {
        "type": "string",
        "minLength": 1
      },
      "startDate": {
        "anyOf": [
          {
            "type": "string",
            "format": "date-time",
            "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
          },
          {
            "type": "null"
          }
        ]
      },
      "description": {
        "type": [
          "string",
          "null"
        ]
      }
    }
  }
}

move_taskTitles 39Descriptions 66Inputs 0Annotations 0Outputs 028/100

Title39/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description66/100

Move a task to another project (and optional column status).

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

destinationProjectId

Not provided

Missing description. Explain what this value means and how to supply it.

destinationStatus

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "move_task",
  "description": "Move a task to another project (and optional column status).",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId",
      "destinationProjectId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "destinationStatus": {
        "type": "string",
        "minLength": 1
      },
      "destinationProjectId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

update_task_statusTitles 56Descriptions 68Inputs 0Annotations 0Outputs 033/100

Title56/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description68/100

Update only the status (column) of a task.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

status

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_task_status",
  "description": "Update only the status (column) of a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId",
      "status"
    ],
    "properties": {
      "status": {
        "type": "string",
        "minLength": 1
      },
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

list_task_commentsTitles 54Descriptions 59Inputs 0Annotations 0Outputs 030/100

Title54/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description59/100

List comments on a task.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_task_comments",
  "description": "List comments on a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

create_task_commentTitles 50Descriptions 61Inputs 0Annotations 0Outputs 030/100

Title50/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description61/100

Add a comment to a task.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

content

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_task_comment",
  "description": "Add a comment to a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId",
      "content"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "content": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

update_task_commentTitles 62Descriptions 62Inputs 0Annotations 0Outputs 033/100

Title62/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description62/100

Update one of your comments on a task.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

commentId

Not provided

Missing description. Explain what this value means and how to supply it.

content

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_task_comment",
  "description": "Update one of your comments on a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "commentId",
      "content"
    ],
    "properties": {
      "content": {
        "type": "string",
        "minLength": 1
      },
      "commentId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

delete_task_commentTitles 58Descriptions 69Inputs 0Annotations 0Outputs 034/100

Title58/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description69/100

Delete one of your comments from a task.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

commentId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_task_comment",
  "description": "Delete one of your comments from a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "commentId"
    ],
    "properties": {
      "commentId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

list_workspace_labelsTitles 58Descriptions 66Inputs 0Annotations 0Outputs 033/100

Title58/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description66/100

List labels defined in a workspace.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

workspaceId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_workspace_labels",
  "description": "List labels defined in a workspace.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "workspaceId"
    ],
    "properties": {
      "workspaceId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

create_labelTitles 51Descriptions 65Inputs 0Annotations 0Outputs 031/100

Title51/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description65/100

Create a label in a workspace (optionally attach to a task).

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

Not provided

Missing description. Explain what this value means and how to supply it.

color

Not provided

Missing description. Explain what this value means and how to supply it.

workspaceId

Not provided

Missing description. Explain what this value means and how to supply it.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_label",
  "description": "Create a label in a workspace (optionally attach to a task).",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "name",
      "color",
      "workspaceId"
    ],
    "properties": {
      "name": {
        "type": "string",
        "minLength": 1
      },
      "color": {
        "type": "string",
        "pattern": "^#(?:[0-9a-fA-F]{3}|[0-9a-fA-F]{6})$"
      },
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "workspaceId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

attach_label_to_taskTitles 51Descriptions 64Inputs 0Annotations 0Outputs 031/100

Title51/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description64/100

Attach an existing label to a task.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

labelId

Not provided

Missing description. Explain what this value means and how to supply it.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "attach_label_to_task",
  "description": "Attach an existing label to a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "labelId",
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "labelId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

detach_label_from_taskTitles 45Descriptions 62Inputs 0Annotations 0Outputs 029/100

Title45/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description62/100

Detach a label from its current task.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

labelId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "detach_label_from_task",
  "description": "Detach a label from its current task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "labelId"
    ],
    "properties": {
      "labelId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

create_task_relationTitles 44Descriptions 75Inputs 0Annotations 0Outputs 032/100

Title44/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description75/100

Create a relation between two tasks. relationType: 'subtask' (sourceTaskId is the parent, targetTaskId the child), 'blocks' (sourceTaskId blocks targetTaskId), or 'related' (bidirectional).

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

sourceTaskId

Not provided

Missing description. Explain what this value means and how to supply it.

targetTaskId

Not provided

Missing description. Explain what this value means and how to supply it.

relationType

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_task_relation",
  "description": "Create a relation between two tasks. relationType: 'subtask' (sourceTaskId is the parent, targetTaskId the child), 'blocks' (sourceTaskId blocks targetTaskId), or 'related' (bidirectional).",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "sourceTaskId",
      "targetTaskId",
      "relationType"
    ],
    "properties": {
      "relationType": {
        "enum": [
          "subtask",
          "blocks",
          "related"
        ],
        "type": "string"
      },
      "sourceTaskId": {
        "type": "string",
        "minLength": 1
      },
      "targetTaskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

get_task_relationsTitles 62Descriptions 70Inputs 0Annotations 0Outputs 035/100

Title62/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description70/100

List all relations (subtask/blocks/related) involving a task.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_task_relations",
  "description": "List all relations (subtask/blocks/related) involving a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

delete_task_relationTitles 50Descriptions 73Inputs 0Annotations 0Outputs 033/100

Title50/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description73/100

Delete a task relation by its relation ID.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_task_relation",
  "description": "Delete a task relation by its relation ID.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

delete_labelTitles 44Descriptions 83Inputs 0Annotations 0Outputs 034/100

Title44/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description83/100

Delete a task or workspace label by ID. Workspace-label cascades resume automatically; repeat the tool if pendingDeletion remains true.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_label",
  "description": "Delete a task or workspace label by ID. Workspace-label cascades resume automatically; repeat the tool if pendingDeletion remains true.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

list_workspace_membersTitles 55Descriptions 76Inputs 0Annotations 0Outputs 035/100

Title55/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description76/100

List the members of a workspace. Use this to resolve the user ID an assignee tool expects.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

workspaceId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_workspace_members",
  "description": "List the members of a workspace. Use this to resolve the user ID an assignee tool expects.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "workspaceId"
    ],
    "properties": {
      "workspaceId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

searchTitles 67Descriptions 68Inputs 65Annotations 0Outputs 053/100

Title67/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description68/100

Search across tasks, projects, workspaces, comments, and activities.

The description explains the capability, when to use it, and what to expect.

Inputs65/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Search query

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

type

Restrict results to one kind. Defaults to all.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

workspaceId

Limit to one workspace

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

projectId

Limit to one project

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

limit

Maximum results, 1 to 50. Defaults to 20.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search",
  "description": "Search across tasks, projects, workspaces, comments, and activities.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "q"
    ],
    "properties": {
      "q": {
        "type": "string",
        "minLength": 1,
        "description": "Search query"
      },
      "type": {
        "enum": [
          "all",
          "tasks",
          "projects",
          "workspaces",
          "comments",
          "activities"
        ],
        "type": "string",
        "description": "Restrict results to one kind. Defaults to all."
      },
      "limit": {
        "type": "integer",
        "maximum": 50,
        "minimum": 1,
        "description": "Maximum results, 1 to 50. Defaults to 20."
      },
      "projectId": {
        "type": "string",
        "minLength": 1,
        "description": "Limit to one project"
      },
      "workspaceId": {
        "type": "string",
        "minLength": 1,
        "description": "Limit to one workspace"
      }
    }
  }
}

list_project_columnsTitles 55Descriptions 61Inputs 0Annotations 0Outputs 031/100

Title55/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description61/100

List a project's columns. Their slugs are the values update_task_status and create_task accept as a status.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

projectId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_project_columns",
  "description": "List a project's columns. Their slugs are the values update_task_status and create_task accept as a status.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "projectId"
    ],
    "properties": {
      "projectId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

delete_taskTitles 46Descriptions 71Inputs 0Annotations 0Outputs 031/100

Title46/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description71/100

Delete a task by ID.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_task",
  "description": "Delete a task by ID.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

update_task_assigneeTitles 44Descriptions 80Inputs 50Annotations 0Outputs 046/100

Title44/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description80/100

Assign a task to a workspace member, or pass a null userId to unassign it.

The description explains the capability, when to use it, and what to expect.

Inputs50/100

1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

userId

Member user ID, or null to unassign

Clear enough to supply this argument.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_task_assignee",
  "description": "Assign a task to a workspace member, or pass a null userId to unassign it.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId",
      "userId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "userId": {
        "anyOf": [
          {
            "type": "string",
            "minLength": 1
          },
          {
            "type": "null"
          }
        ],
        "description": "Member user ID, or null to unassign"
      }
    }
  }
}

update_task_due_dateTitles 37Descriptions 79Inputs 0Annotations 0Outputs 031/100

Title37/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description79/100

Set a task's due date. Omit dueDate to clear it.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

dueDate

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_task_due_date",
  "description": "Set a task's due date. Omit dueDate to clear it.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "dueDate": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      }
    }
  }
}

list_task_time_entriesTitles 60Descriptions 70Inputs 0Annotations 0Outputs 035/100

Title60/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

List the time entries logged against a task.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_task_time_entries",
  "description": "List the time entries logged against a task.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

get_time_entryTitles 55Descriptions 72Inputs 0Annotations 0Outputs 034/100

Title55/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description72/100

Get a single time entry by ID.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_time_entry",
  "description": "Get a single time entry by ID.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

create_time_entryTitles 40Descriptions 74Inputs 0Annotations 0Outputs 030/100

Title40/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description74/100

Log time against a task. Omit endTime to leave the entry running.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

startTime

Not provided

Missing description. Explain what this value means and how to supply it.

endTime

Not provided

Missing description. Explain what this value means and how to supply it.

description

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_time_entry",
  "description": "Log time against a task. Omit endTime to leave the entry running.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId",
      "startTime"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      },
      "endTime": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "startTime": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "description": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

update_time_entryTitles 54Descriptions 70Inputs 0Annotations 0Outputs 033/100

Title54/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

Update a time entry. startTime is required; omitting endTime keeps the stored one. startTime cannot be later than the end time.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Not provided

Missing description. Explain what this value means and how to supply it.

startTime

Not provided

Missing description. Explain what this value means and how to supply it.

endTime

Not provided

Missing description. Explain what this value means and how to supply it.

description

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_time_entry",
  "description": "Update a time entry. startTime is required; omitting endTime keeps the stored one. startTime cannot be later than the end time.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id",
      "startTime"
    ],
    "properties": {
      "id": {
        "type": "string",
        "minLength": 1
      },
      "endTime": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "startTime": {
        "type": "string",
        "format": "date-time",
        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
      },
      "description": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

list_task_activityTitles 46Descriptions 65Inputs 0Annotations 0Outputs 030/100

Title46/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description65/100

List a task's activity history.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

taskId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_task_activity",
  "description": "List a task's activity history.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "taskId"
    ],
    "properties": {
      "taskId": {
        "type": "string",
        "minLength": 1
      }
    }
  }
}

list_notificationsTitles 60Descriptions 68Inputs 100Annotations 0Outputs 061/100

Title60/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description68/100

List the signed-in user's notifications.

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_notifications",
  "description": "List the signed-in user's notifications.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01Search across tasks, projects, workspaces, comments, and activities
02Get task by ticket idGet one task by its ticket ID (project key and number, e.g.
03Get a single project by ID
04List the signed-in user's notifications
05List workspacesList workspaces (Better Auth organizations) the signed-in user can access.

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

Overview

Category: Productivity

FAQ

kaneo-mcp setup, tools, quality score, publishing readiness, and alternatives.

How do I add kaneo-mcp to Claude, ChatGPT, or Cursor?

Add kaneo-mcp to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://cloud.kaneo.app/api/mcp.

Is kaneo-mcp MCP ready for ChatGPT and Claude?

As of October 16, 2026, kaneo-mcp scores 82/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and does not yet meet Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is kaneo-mcp's MCP tool documentation?

As of October 16, 2026, kaneo-mcp scores 36/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 38 of 38 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What are the best alternatives to kaneo-mcp?

As of October 20, 2026, alternatives to kaneo-mcp in productivity on the Manufact MCP leaderboard include Autodesk Product Help, BoardWise, FlagStat, Keenable Web Search, and PomoDial.

How can kaneo-mcp improve its MCP documentation?

move_task is the lowest-scoring reviewed tool at 28/100. 0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…