Skip to main content
Glama
Sign In
gold-mcp

gold-mcp

by ThaiTrevor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_macro_context

Retrieve a macro snapshot of key indicators relevant to gold, including DXY, US10Y/02Y, SPX, VIX, BTC, silver, and oil, to understand the market context driving gold prices.

Instructions

Macro snapshot relevant to gold: DXY, US10Y/02Y, SPX, VIX, BTC, silver, oil.

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_macro_context"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.2

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only lists the asset names and says 'snapshot', but does not describe output format, data recency, whether values are real-time or delayed, or any other operational traits.

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 a single front-loaded sentence that efficiently conveys the tool's content. Every word earns its place and there is no extraneous information.

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

Completeness3/5

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

The description lists the included macro indicators, which is useful for a zero-parameter tool. However, without an output schema or annotations, it lacks information about the returned data structure, time period, or precision, leaving some gaps for the agent.

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 has zero parameters, so the baseline is 4 per the rubric. There is no parameter schema to explain, and the description is not expected to add parameter detail beyond that.

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 clearly states the tool provides a macro snapshot relevant to gold, listing specific instruments (DXY, US10Y/02Y, SPX, VIX, BTC, silver, oil). It is specific and not a tautology, though it does not explicitly differentiate from sibling tools like get_gold_price or get_vn_macro.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives, nor any exclusions or context. The phrase 'relevant to gold' implies a high-level macro context role, but there is no explicit recommendation or comparison with sibling tools.

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

Deploy Server

Other Tools