CNBS MCP Server

Fetch CNBS Metrics

cnbs_fetch_metrics

Read-onlyIdempotent

Retrieve all available metrics from one or more datasets using dataset IDs. Supports filtering by metric name for a single dataset. Returns metrics grouped by dataset ID for batch queries.

Instructions

根据数据集ID (setId) 获取所有可用指标列表。支持同时查询多个数据集。

Args:

setIds (string | string[]): 单个或多个数据集ID，来自 cnbs_search 或 cnbs_fetch_nodes 的 isEnd=true 节点
name (string): 指标名称过滤（可选，单个 setId 时有效）

Returns: 指标列表，多个 setId 时返回按 setId 分组的结果

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "setIds": "<setIds>"
    },
    "name": "cnbs_fetch_metrics"
  }
}

Input Schema

Name	Required	Description	Default
`setIds`	Yes	单个或多个数据集ID
`name`	No	指标名称过滤（可选）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Apr 25, 2026

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint, and openWorldHint. The description adds that results are grouped by setId when multiple setIds are provided, which is a behavioral detail beyond annotations. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with an Args and Returns section, front-loading key information. No unnecessary sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains the return structure (grouped by setId for multiple inputs). It covers both parameters adequately, though it does not address error scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by specifying that setIds come from specific sources and that name filtering is only for single setId. This aids correct invocation beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches all available metrics for given dataset IDs, specifying it can handle multiple setIds. It distinguishes itself from sibling tools like cnbs_search and cnbs_fetch_nodes by focusing on metrics retrieval after dataset identification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear context on when to use: after obtaining setIds from cnbs_search or cnbs_fetch_nodes with isEnd=true. It also notes that name filtering is optional and only effective with a single setId. However, it does not explicitly state when not to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.