SiteCheck Trade & Energy

US producer price index for wood pulp, monthly index value

energy_pulp_paper_risi_index

Read-only

US producer price index for wood pulp (BLS series WPU0911, via FRED), monthly index value. This is a price index, not the RISI Northern Bleached Softwood Kraft (NBSK) benchmark; the route name is kept for the owner. Latest value plus up to 24 months of history. Related tools on this server, for a different need: energy_fao_food_price_index when you need FAO Food Price Index monthly values from the FAO CSV; logistics_jet_a1_fuel_index when you need daily US Gulf Coast kerosene-type jet fuel spot price. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "energy_pulp_paper_risi_index"
  }
}

Input Schema

Name	Required	Description	Default
`months`	No	Months of history, 1 to 24 (default 3)

Output Schema

Name	Required	Description	Default
`unit`	No
`latest`	No
`series`	No
`source`	No
`history`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only and open-world, so the bar is lower, yet the description adds real behavior: return scope ('latest value plus up to 24 months of history'), the underlying series provenance, and a full payment model ($0.002 USDC per successful call via x402 on Base/Solana/Arc, failed calls not charged). Rate limits and latency are not mentioned, keeping it short of a 5.

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 core purpose, the RISI disambiguation, and the return scope are front-loaded and tight. The sibling-tool list and pricing block make the tail longer than necessary for a single-parameter index tool, but each sentence still carries routing or billing value.

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?

An output schema exists, so return-value explanation is not required, and the description still adds source provenance, history window, and cost model. For a one-parameter, read-only index tool with annotations, nothing an agent needs in order to call it correctly is missing.

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

Parameters3/5

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

Only one optional parameter with 100% schema description coverage, so the schema already carries the semantics ('Months of history, 1 to 24 (default 3)'). The description restates the 24-month ceiling but adds no format, default, or edge-case detail beyond what the schema gives. Baseline 3 applies.

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 resource and measure: 'US producer price index for wood pulp (BLS series WPU0911, via FRED), monthly index value.' It also pre-empts the obvious mismatch between the tool name ('risi_index') and the actual data, explicitly noting it is NOT the RISI NBSK benchmark. An agent can distinguish this from every other price-index sibling without opening the schema.

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?

Provides clear when-not guidance ('not the RISI NBSK benchmark') and names two alternatives with the condition that selects each ('energy_fao_food_price_index when you need FAO Food Price Index monthly values', 'logistics_jet_a1_fuel_index when you need daily US Gulf Coast jet fuel spot price'). What's missing is a positive statement of the scenario that should select this tool, though the intent is strongly implied.

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

All SiteCheck Trade & Energy 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?