Skip to main content
Glama

Macro & Commodities Desk

by com.predictionmarketspicks
OverviewDiscussionsAdmin

Market Pulse — Macro

market_pulse
Read-only

The US macro-health composite (0–100) and regime plus the six category scores (growth, labor, inflation, rates, liquidity, sentiment). Returns the composite, the regime call and 2 category scores without an account, 4 to a signed-in account, and all six with Pro. Use for "how is the US economy", "macro regime", "risk-on or risk-off".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNomacro = the US macro-health composite (the only topic). One of: macro.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / topic / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "enum": [
+      "macro"
+    ],
+    "type": "string"
+  }
+]
    • removedInput schema / properties / topic / default
      Removed value: -"macro"
    • changedInput schema / properties / topic / description
      Previous value: -"macro = the US macro-health composite (the only topic)."New value: +"macro = the US macro-health composite (the only topic). One of: macro."
    • removedInput schema / properties / topic / enum
      Removed value: -[
-  "macro"
-]
    • removedInput schema / properties / topic / type
      Removed value: -"string"
  2. Changed1 schema field changed
    • changedInput schema / properties / topic / description
      Previous value: -"macro = US macro-health composite (the only topic — NFL is now the nfl_edge tool)."New value: +"macro = the US macro-health composite (the only topic)."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, openWorld), and the description adds the crucial behavioral detail annotations cannot: tiered access gating — composite/regime/2 categories unauthenticated, 4 signed in, all six with Pro. That is exactly the auth/permission context an agent needs before calling.

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?

Three sentences, each carrying distinct load: what it returns, what access tier yields what, and when to use it. Front-loaded with the resource and no filler.

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

Completeness5/5

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

With no output schema, the description correctly spells out the return payload (composite, regime call, category scores) and qualifies it by tier. Nothing an agent needs to invoke or interpret the result is missing.

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

Parameters3/5

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

Only one optional parameter, and schema coverage is 100% — the schema already documents that 'macro' is the sole topic. The description restates the composite concept but adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a specific resource (US macro-health composite, regime, six category scores) with a clear scope (0-100 composite, regime call). An agent can immediately tell this apart from the sibling odds/political tools, none of which touch 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 Guidelines4/5

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

Provides explicit trigger phrases — "how is the US economy", "macro regime", "risk-on or risk-off" — so the agent knows the intent this tool serves. It names no alternative tools or when-not-to-use conditions, but the siblings are unrelated domains, so the gap is minor.

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

All Macro & Commodities Desk toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources