Trustbase Lab · Trusted Data Infrastructure for the AI Era

Grade Price Trend

get_grade_trend

Read-onlyIdempotent

Purpose: return the historical series of the layered rCB index for one grade tier - period-by-period assessed benchmark price, period-on-period change, anchor, adjustment factor and verification factor. Guidelines: grade defaults to P2 in the CN region; set start_date and end_date as YYYY-MM to slice a window; pair with get_rcb_index for the current cross-section and get_price_trend for category-level trends. Limits: index points only - dimensionless, non-tradable, and never to be converted into an absolute price; early periods may carry an anchor carried forward from an earlier month, and the output flags when this happens. Ex: get_grade_trend(grade='P2'), get_grade_trend(grade='P1', start_date='2025-12', end_date='2026-09').

Input Schema

TableJSON Schema

Name	Required	Description
`grade`	No	层级，默认 P2
`region`	No	区域，默认 CN
`end_date`	Yes	结束期 YYYY-MM
`start_date`	Yes	起始期 YYYY-MM

Output Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Human-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "text": {
+      "description": "Human-readable result (markdown, or a JSON string when response_format=json).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}

AddedSep 17, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already establish read-only, idempotent, and non-destructive behavior. The description adds valuable non-obvious context: the index is dimensionless, non-tradable, must never be converted to an absolute price, and early periods may carry forward an anchor with output flags.

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

Conciseness5/5

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

The description is organized into Purpose, Guidelines, Limits, and Ex sections. It is compact, front-loaded with the core purpose, and every sentence carries actionable information without redundancy.

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

Completeness5/5

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

For a tool with an output schema, rich annotations, and only four parameters, the description is fully complete. It covers what the tool returns, how to call it, how it relates to siblings, and important interpretive caveats.

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%, so the baseline is 3. The description adds meaningful value beyond the schema by explaining defaults (P2, CN), the YYYY-MM date format, and providing usage examples for valid parameter combinations.

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 states a specific verb and resource: 'return the historical series of the layered rCB index for one grade tier.' It names the exact fields returned and clearly distinguishes this tool from siblings like get_rcb_index and get_price_trend.

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

Usage Guidelines5/5

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

Provides explicit guidance: grade defaults to P2 in CN, date format must be YYYY-MM, and pairing with get_rcb_index or get_price_trend is recommended for different analytical needs. It also includes concrete examples showing valid calls.

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

All Trustbase Lab · Trusted Data Infrastructure for the AI Era tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?