continuedev / continuedev/continue

Invalid names of tools being called

Open
#13,047 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
Relevant environment info
- OS: MacOS
- Continue version: 2.0.0
- IDE version: VSCode 1.20.0
- Model: Qwen3.6-35B-A3B
- config:

name: Local Config
version: 1.0.0
schema: v1
models:
  - name: local-mac
    provider: ollama
    apiBase: http://localhost:11434/
    model: AUTODETECT
    systemMessage: You are expert software developer.
  
- mcp config:

name: localMCP
version: 1.0.0
schema: v1
mcpServers:
  - name: jira_mcp
    type: streamable-http
    url: http://localhost:8089/mcp
    env: {}
  - name: bitbucket_mcp
    type: streamable-http
    url: http://localhost:8096/mcp
    env: {}
Description

When I ask Qwen3.6-35B-A3B:

What Jira ticket TICKET-38520 is all about?

I get error, because it tries call tool that do not exist:

The user is asking for information about a specific Jira ticket, identified as "TICKET-38520". I need to use the jira_mcp_get_jira_ticket tool to fetch the details of this ticket. The tool requires one argument: jiraID. The value for jiraID is "TICKET-38520".

Plan:

Call jira_mcp_get_jira_ticket with jiraID set to "TICKET-38520".
Once the information is retrieved, present it to the user.
Current step: Call the tool.

The problem is that tool name is get_jira_ticket not jira_mcp_get_jira_ticket.

Here is the MCPJira schema:

{
  "jsonrpc": "2.0",
  "result": {
    "tools": [
      {
        "name": "get_jira_ticket",
        "inputSchema": {
          "properties": {
            "jiraID": {
              "type": "string",
              "description": "jiraID"
            }
          },
          "type": "object",
          "required": [
            "jiraID"
          ]
        },
        "description": "Returns Jira ticket info for given jiraID"
      },
      {
        "name": "get_jira_attachment",
        "inputSchema": {
          "type": "object",
          "required": [
            "attachmentPath"
          ],
          "properties": {
            "attachmentPath": {
              "type": "string",
              "description": "attachmentPath defined in jira response"
            }
          }
        },
        "description": "Allows to download attachment by its attachmentPath"
      }
    ]
  },
  "id": 1
}
To reproduce

No response

Log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how Continue consumes the MCP schema and constructs tool names, using the supplied get_jira_ticket schema and error output as the reproduction. Verify the generated call against the server's declared tool name and confirm that Jira and other MCP tools can be invoked without an invalid prefix.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.