Skip to content

bug: Model is overloaded with toolsΒ #29

@Nek-12

Description

@Nek-12

Not all mcp frontends (example: Claude Code) support disabling and hiding tools.

You severely overload the model with tools.
You need to keep the tool count below 15, maximally 20. Many of the tools could be merged.

  • list_workspace_members() could return the current user first (no get_user tool)
  • get_issue_type should just be an output of list_issue_types
  • create/update/delete issue types could be an upsert call. deleting types and even changing them is arguably less needed.
  • states and related tools should be one tool to list states. arguably, deleting is not important for an mcp
  • same story with labels. do we need such precise tag management? But in my opinion more important than deleting states.
  • adding issues: this should just support module, project, status, cycle and labels as a parameter. why is it split between creating module issues, project issues, and cycle issues?
  • issue worklogs should just be an optional output of the get issue details tool. cruds can be replaced with an upsert.
  • get cycle should be an output of list cycles.

I just eliminated 8-15 tools.

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions