Skip to main content
Glama
Sign In
gold-mcp

gold-mcp

by ThaiTrevor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_vn_macro

Fetches USD/VND exchange rate, cross rates, and world-parity gold price in VND for Vietnam market context.

Instructions

USD/VND + cross rates + implied world-parity gold price in VND.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.1.2

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It reveals the data categories but not whether this is a read-only market snapshot, how current the data is, whether it is computed/cached, or what units/formats are returned. The phrase 'implied world-parity' hints at calculation but lacks detail.

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 compact fragment that conveys the essential content in under 90 characters. No filler or redundant detail. It is front-loaded and easy to parse.

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 parameterless tool with no output schema, the description names the key return values, which is largely sufficient. However, it lacks an explicit statement of how the result is structured (e.g., object with keys for usd_vnd, cross_rates, gold_vnd) or any caveats, so it is not fully complete.

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. There is nothing to document, and the description does not introduce parameter confusion. It correctly implies a parameterless request.

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 enumerates the tool's content: USD/VND rate, cross rates, and implied world-parity gold price in VND. Although it lacks an explicit verb, the name 'get_vn_macro' and the listed outputs make the purpose unambiguous. It differentiates from sibling tools like get_gold_price and get_macro_context by specifying VND-centric macro data.

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?

There is no guidance on when to choose this tool over siblings such as get_macro_context or estimate_vn_gold_premium. The description only states what the tool returns, leaving the agent to infer use cases. No exclusions or alternatives are mentioned.

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