Skip to main content
Glama

Stratalize Intelligence

Get Copper Price Benchmark

get_copper_price_benchmark
Read-only

IMF Grade A copper price in USD per metric ton with year-over-year change and industrial demand significance note. Use as a coincident indicator for global manufacturing and construction cycles. Source: FRED / IMF. $0.02 atomic. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: a $0.02 per-call charge, a post-quantum signed settlement receipt, and a verification URL. The only weakness is that the '$0.02 atomic' phrasing is opaque and the cost is stated twice without clarifying billing mechanics.

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

Conciseness3/5

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

The first two sentences are well front-loaded and earn their place. The trailing trust and payment boilerplate is somewhat redundant, repeating '$0.02' in two different notations ('$0.02 atomic' and '$0.02 USDC per call') and adding a marketing-style verification line that could be compressed to a single clause.

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?

For a zero-parameter read tool with no output schema, the definition covers the essentials: what value is returned, its units, its source (FRED / IMF), the derived fields (YoY change, demand note), and the cost. An agent could invoke it correctly without further information; only billing mechanics remain slightly ambiguous.

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?

The tool takes zero parameters, so per the baseline a 4 applies. The description correctly implies a parameterless call by describing only the returned measurement and its source, leaving nothing for an agent to guess about input.

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

Purpose4/5

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

The description names a specific resource with units and provenance: 'IMF Grade A copper price in USD per metric ton with year-over-year change and industrial demand significance note.' An agent knows exactly what data it receives. It stops short of distinguishing itself from near-siblings like get_commodity_benchmark, but the resource specificity is strong.

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

Usage Guidelines3/5

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

'Use as a coincident indicator for global manufacturing and construction cycles' gives a clear analytical use case, which is better than nothing. However, there is no when-not-to-use guidance, no mention of when a sibling commodity or macro benchmark would be preferable, and no stated preconditions for calling it.

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