Skip to content

fix: MCP writeNoSqlDatabaseContent 缺少嵌套对象部分更新的清晰文档与示例,易导致整块替换而非局部更新#691

Open
binggg wants to merge 1 commit intomainfrom
automation/attribution-issue-mojxi9ss-hae7qn-mcp-writenosqldatabasecontent
Open

fix: MCP writeNoSqlDatabaseContent 缺少嵌套对象部分更新的清晰文档与示例,易导致整块替换而非局部更新#691
binggg wants to merge 1 commit intomainfrom
automation/attribution-issue-mojxi9ss-hae7qn-mcp-writenosqldatabasecontent

Conversation

@binggg
Copy link
Copy Markdown
Member

@binggg binggg commented Apr 29, 2026

Attribution issue

  • issueId: issue_mojxi9ss_hae7qn
  • category: tool
  • canonicalTitle: MCP writeNoSqlDatabaseContent 缺少嵌套对象部分更新的清晰文档与示例,易导致整块替换而非局部更新
  • representativeRun: atomic-js-none-update-nosql-nested-object-implicit/2026-04-29T10-43-30-4c5bj3

Automation summary

  • root_cause: The writeNoSqlDatabaseContent MCP tool's description and update parameter description mentioned using dot notation for nested field updates, but the warning was generic and lacked concrete JSON examples showing the exact WRONG vs CORRECT $set payload format. When an agent saw a prompt like "update shipping to {city: guangzhou}", it naturally translated this into $set: { "shipping": { "city": "guangzhou" } } (replacing the entire object) instead of $set: { "shipping.city": "guangzhou" } (partial update). The abstract address.city example didn't clearly show the JSON structure difference.
  • changes: (1) In mcp/src/tools/databaseNoSQL.ts, enhanced the tool description with a prominent ⚠️ warning showing both the WRONG $set: {"shipping": {"city": "guangzhou"}} and CORRECT $set: {"shipping.city": "guangzhou"} JSON payloads. (2) In the update parameter description, added a / block with the same concrete WRONG vs CORRECT JSON examples, plus a backtick-wrapped shipping.city code reference. (3) Updated mcp/src/tools/databaseNoSQL.test.ts to assert the new shipping.city reference instead of the old address.city.
  • validation: All 15 databaseN

Changed files

  • mcp/src/tools/databaseNoSQL.test.ts
  • mcp/src/tools/databaseNoSQL.ts

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@binggg
Copy link
Copy Markdown
Member Author

binggg commented Apr 29, 2026

Attribution post-PR evaluation

  • visibility: internal identifiers, run ids, and private links are intentionally omitted
  • attempt: 1
  • eval_scope: primary_only
  • overall: FAILED
  • summary: at least one planned evaluation case failed
  • updated_at: 2026-04-29T10:59:52.578Z

Cases

  • [FAILED] — primary — evaluation failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant