Skip to main content
Glama

BRAINIAC Global Financial Markets & Macro Intelligence

Profile country macro risk

macro-intelligence_country-risk-profile

Summarize supplied inflation, policy rates, and debt into a descriptive risk level. This is not a credit rating. Price $0.05 USDC. POST /api/v1/macro-intelligence/country-risk-profile. Unpaid calls return 402 and do not run.

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": "macro-intelligence_country-risk-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
debtNo
fileNo
jsonNo
textNo
ratesNo
eventsNo
seriesNo
tenorsNo
releasesNo
worldBankNo
commoditiesNo
priceLevelsNo
observationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it usefully discloses pricing, the POST endpoint, and the unpaid-call 402/no-run behavior. It does not explain data handling, validation, or the return shape beyond the vague 'descriptive risk level'.

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?

Four short sentences, front-loaded with the purpose and then operational terms, with no filler. The not-a-credit-rating caveat and payment/failure details all earn their place.

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

Completeness2/5

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

This is a complex 15-parameter tool with nested objects, no required fields, no annotations, and no output schema. The description covers the paid-call mechanics and a high-level purpose but leaves the data-supply model, parameter selection, and result format largely unexplained, so it is not complete enough for correct invocation.

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

Parameters2/5

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

With 15 parameters and 0% schema description coverage, the description should map and explain inputs; instead it names only three broad data domains. It does not explain csv/json/text/file alternatives, asOf, arrays, limits, or nested structures.

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?

States a specific verb ('Summarize') and the resources ('inflation, policy rates, and debt') plus the output concept ('descriptive risk level'), which is more than a restatement of the name. It also sets a scope boundary ('not a credit rating'), but it does not distinguish this from siblings such as sovereign-debt-maturity-analyze or yield-curve-analyze.

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?

The description implies use when you have macro inputs and want a descriptive country risk summary, and it warns that the output is not a credit rating. It does not state when to choose this over sibling analyses or what input conditions are required.

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