Skip to main content
Glama

macro_dashboard

🔒 PREMIUM (not available anonymously on this endpoint): Full US economic dashboard — all key indicators at once: Fed, inflation, yields, labor, GDP, housing.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose a genuine behavioral constraint — the tool requires premium authentication and fails for anonymous callers — which is valuable. It says nothing about what the returned payload looks like, freshness, or per-indicator availability.

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?

A single sentence plus an explicit premium flag; the access caveat is front-loaded and the indicator list is dense but purposeful. Nothing is redundant.

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 zero-parameter aggregation tool with no output schema, the description tells an agent what it gets back at a coarse level and warns of the auth barrier, which is the key decision input. It could note whether individual indicators can be retrieved from this tool or only in aggregate, but the essentials are present.

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, so there is no parameter meaning to add and the baseline is 4. The description correctly implies no arguments are needed by framing it as a single all-at-once dashboard.

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 aggregate resource and enumerates its contents (Fed, inflation, yields, labor, GDP, housing), which clearly distinguishes it from the single-indicator siblings like bls_inflation or yield_curve. It stops short of explicitly saying 'use this instead of calling the individual tools'.

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?

Usage is implied by 'all key indicators at once', suggesting a broad overview rather than a targeted lookup, and the individual indicator siblings are visible in the tool list. However, no explicit when-to-use or when-not-to-use statement is given, and the anonymous-access restriction is stated as a status rather than guidance on the fallback.

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.