Skip to main content
Glama

Trustbase Lab · Trusted Data Infrastructure for the AI Era

estimate_rcb_price

estimate_rcb_price
Read-onlyIdempotent

Purpose: estimate an rCB reference price by multiplying a dated export-price anchor by a grade-tier discount and a regional coefficient, and explicitly state whether the result may be quoted externally. Guidelines: use for "what should rCB cost / how much cheaper than virgin / what budget should I plan" questions; always report the tier, region and period. Limits: this is an INDEX-DERIVED value, NOT a transactable quote; the anchor is an all-grades export average skewed to mid/low quality; only the CN regional coefficient is calibrated - EU/NA/SEA coefficients are uncalibrated and marked non-releasable, so those results are order-of-magnitude only. Ex: estimate_rcb_price(tier='P2', region='CN'), estimate_rcb_price(tier='P1', quantity=100).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "estimate_rcb_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNo档位:P1 精制 ρ=0.90 / P2 标准 ρ=0.80 / P3 工业 ρ=0.60P2
periodNo期间 YYYY-MM;不填用最新(当前 2025-12)
regionNo区域;仅 CN 系数已校准可对外,其余为量级参考CN
quantityNo数量(吨,可选);给了会算总金额
response_formatNoOutput format: 'markdown' (default, human-readable) or 'json' (machine-readable).markdown

Output Schema

NameRequiredDescriptionDefault
textYesHuman-readable result (markdown, or a JSON string when response_format=json).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world operation, so the safety profile is covered. The description adds substantial behavior beyond that: the value is index-derived rather than transactable, the anchor is an all-grades export average skewed to mid/low quality, and only the CN coefficient is calibrated while EU/NA/SEA results are flagged non-releasable and order-of-magnitude only. This is exactly the caveat context an agent needs before quoting a number.

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?

Front-loaded with an explicit Purpose/Guidelines/Limits/Ex structure so an agent can skim to the constraint it needs, and the critical 'not a quote' warning lands early. It is dense but every clause carries a distinct constraint; only the example line is mildly redundant with the schema.

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 five-parameter estimation tool with an output schema already covering return values, the description supplies everything else: the formula, the trigger use cases, the data-quality caveats, and the per-region releasability rule that determines whether the answer can be shown externally.

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 description coverage is 100%, so the tier discount ratios, period format, region calibration note and quantity-as-tons are already documented in the schema. The description still adds value by showing realistic parameter combinations (tier='P2', region='CN' vs. tier='P1', quantity=100) and by requiring tier/region/period to be reported alongside the result.

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?

States a specific verb (estimate) and resource (rCB reference price) and spells out the computation (export-price anchor × grade-tier discount × regional coefficient) plus the releasability determination. This is clearly distinguishable from sibling index/benchmark lookups like get_rcb_index or get_price_benchmark.

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?

Gives concrete trigger questions ('what should rCB cost', 'how much cheaper than virgin', 'what budget should I plan') and a clear when-not boundary (not a transactable quote). It does not explicitly route to a sibling tool for the alternative case (e.g., a raw index or benchmark lookup), which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources