MoonshotAI / MoonshotAI/kimi-cli

[mcp error]"tools.function.parameters is not a valid moonshot flavored json schema, details: <At path 'properti es.assetRef': conflicting keywords found after $ref expansion: description>", 'type': 'invalid_request_error'}

Open
#2,061 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
11.4k
Forks
1.3k
Avg merge
9h 47m
Merged PRs (30d)
2

Description

What version of Kimi Code CLI is running?

1.39.0

Which open platform/subscription were you using?

kimi code

Which model were you using?

k2.6

What platform is your computer?

windows

What issue are you seeing?

i am using a mcp(https://github.com/IvanMurzak/Unity-MCP) for unity,when config mcp with kimi cli.erorr comes;LLM provider error: Error code: 400 - {'error': {'message': "tools.function.parameters is not a valid moonshot flavored json schema, details: <At path 'properti
es.assetRef': conflicting keywords found after $ref expansion: description>", 'type': 'invalid_request_error'}}

What steps can reproduce the bug?

session-6b9bb78e-6401-4399-9827-60a54fdad4f2.zip

What is the expected behavior?

No response

Additional information

No response

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 reproducing the MCP configuration with Unity-MCP on Kimi Code CLI 1.39.0 using the attached session archive, then trace handling of the tool schema around the reported properties.assetRef error. Done means the configuration no longer produces the invalid Moonshot JSON Schema request, or the incompatibility is clearly reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, unity
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.