fix: MCP 工具缺失：NoSQL 数据库回档时间查询能力

[binggg]

Attribution issue

• issueId: issue_mo4ea1oa_jz44d0
• category: tool
• canonicalTitle: MCP 工具缺失：NoSQL 数据库回档时间查询能力
• representativeRun: atomic-js-cli-tcb-db-nosql-backup-time/2026-04-21T17-29-35-whmbre

Automation summary

• root_cause: The MCP tools for NoSQL database were missing a tool to query backup/restore time range (回档时间). The evaluation expected a command like tcb db nosql backup time to query the backup time range, but this tool did not exist in the toolset.
• changes: Added a new tool queryNoSqlDatabaseBackupTime in mcp/src/tools/databaseNoSQL.ts with the following features:
• Tool name: queryNoSqlDatabaseBackupTime
• Purpose: Query NoSQL database backup/restore time range
• Parameters: collectionName (optional, for collection-specific queries) and instanceId (optional, for explicit instance specification)
• API call: Uses CloudBase API action DescribeBackupTime with EnvId, TableName, and Tag parameters
• Returns: JSON response with backupTimeRange containing earliestTime, latestTime, startTime, endTime, plus instanceId and collectionName
• Annotations: Marked as readOnlyHint: true and categorized under "NoSQL database"
• validation:
• TypeScript compilation passes with no errors
• All 15 existing NoSQL database tests pass
• All 10 skill-related regression tests pass (build-skills-repo, build-compat-config, skill-quality-standards)
• **follow

Changed files

• mcp/src/tools/databaseNoSQL.ts

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 320dcad7d7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use DescribeRestoreTime API contract for backup-time query

This new tool calls commonService("tcb", "2018-06-08") with Action: "DescribeBackupTime" and params TableName/Tag, but the repository’s CloudBase manager docs for “查询可回档时间” specify commonService('flexdb').call with Action: 'DescribeRestoreTime' and Param.InstanceId. In environments that follow the documented contract, this request shape can fail outright or hit a different backend action, so users asking for restoreable timestamps may not get a valid response.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Return documented restore-time fields from API response

The response formatter reads EarliestTime/LatestTime/StartTime/EndTime, but the documented restore-time response uses RestoreTimes (and optionally RestoreTimeRanges). If the API returns the documented fields, this tool will emit backupTimeRange with null/empty values even when the call succeeds, which breaks downstream consumers expecting actual restore-time data.

Useful? React with 👍 / 👎.

[binggg]

Attribution post-PR evaluation

• visibility: internal identifiers, run ids, and private links are intentionally omitted
• attempt: 1
• eval_scope: primary_only
• overall: PASSED
• summary: all planned evaluation cases passed
• updated_at: 2026-04-29T00:04:44.817Z

Cases

• [PASSED] — primary — evaluation passed

[binggg]

参考 review 提出的问题

1. 应该参考 manager sdk 的文档实现，当前 PR 的实现也有问题，不符合我原来设计的不增加额外 tool 的原则

重新进行实现和修复，并更新相关的原则，避免再犯

[binggg]

经过真实回归测试，PR #670 当前代码存在 API 契约错误，无法正确工作。以下是详细分析：

回归方式
在本地构建 PR 分支 MCP (320dcad) 并通过 --mcp --mcpPackage 注入定向评测
实测结果
Run | 状态 | Score | 时长 | 关键问题 -- | -- | -- | -- | -- 2026-04-29T08-37-20-y1rc83 | pass (假阳性) | 0.935 | 340s / 62 turns | 新工具始终报错，agent 被迫绕路
核心问题（与 Review 意见一致）

1. API 契约错误

ts
复制
插入
新建文件
保存
应用
// PR 实际代码
commonService("tcb", "2018-06-08").call({
Action: "DescribeBackupTime", // ❌ 不存在
Param: { TableName, Tag } // ❌ 参数名错误
})
// 正确应为
commonService("flexdb", ...).call({
Action: "DescribeRestoreTime", // ✅
Param: { InstanceId } // ✅
})

2. 返回字段错误

PR 读取 EarliestTime/LatestTime/StartTime/EndTime
实际应读取 RestoreTimes / RestoreTimeRanges
Trace 关键证据
agent 调用 queryNoSqlDatabaseBackupTime 时始终收到：

[DescribeBackupTime] The request action=DescribeBackupTime is invalid or not found in service=tcb and version=2018-06-08

agent 被迫花费 340 秒、62 turns 尝试绕路（换 service、WebFetch 查文档、callCloudApi 猜 action），最终只能写一份包含错误说明的 RESULT.json，grader 因关键词匹配而误判 pass。