Skip to main content
Glama

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

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false), so the marginal bar is low, and the description still adds real context beyond them: the data source (FRED / IMF), a per-call cost of $0.02 USDC, and a cryptographic settlement receipt with a verification URL. Those payment and provenance facts materially affect whether and how an agent invokes the tool. It says nothing about caching, rate limits, or latency, so a 4 rather than 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?

It is front-loaded: what the tool returns first, then how to use it, then provenance and payment. The only waste is the repeated price figure ('$0.02 atomic' and '$0.02 USDC per call') and a somewhat promotional attestation sentence, which together cost it a point.

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?

With no parameters, no output schema, and annotations already carrying the safety profile, the description does the remaining work: it specifies units, what the payload contains, the source, and the payment requirement. Return-value structure is described only loosely (no field names or format), which is the one gap for a tool with no output schema.

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 and the schema is an empty object, so there is no parameter meaning to add; the baseline of 4 applies. The description correctly implies a no-argument call by framing the tool as a fixed benchmark lookup.

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 (IMF Grade A copper price), its unit (USD per metric ton), and its payload (year-over-year change plus an industrial demand note), so an agent knows exactly what comes back. It does not name a differentiating sibling such as get_commodity_benchmark, so it falls short of the explicit sibling-differentiation bar for a 5.

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 gives a clear use context: 'Use as a coincident indicator for global manufacturing and construction cycles.' That tells the agent which analytical question this tool answers. There is no when-not guidance and no named alternative among the many other benchmark tools, which keeps it out of 5 territory.

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