Skip to content

Possible Bug in tool calls & Feature Request: Way to debug tool errors #417

@ddevz

Description

@ddevz

I got a "Failed to parse tool call" ... "undetermined string literal (detected at line 1) (, line 1)" on a UpdateTodoList call. However, I dont see anything wrong with what the AI json request.

FEATURE REQUEST:
So my feature request is a "/tool" command to be able to run tool calls myself

It's for testing purposes. I'd like to cut and paste a copy of the AI json to the tool to recreate the error, so something like:

/tool {"name": "UpdateTodoList", "arguments": {"content": "whatever it said"}}

to regenerate the error, then start using variations to find what the issue is.

POSSIBLE BUG:
"undetermined string literal (detected at line 1) (, line 1)"

the UpdateTodoList request had a \n in the content string between each todo item... could that be the parsing problem?

cecli v0.95.11
Model: ollama/quen3-coder:30B with agent edit format
MCP servers configured: Local

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions