Skip to main content
Glama

Industry Dashboard

industry_dashboard
Read-only

Composite industry terminal dashboard payload. (Source: FFIEC + FDIC + FRED.) Dollar amounts are in whole US dollars (not thousands); ratios are percentages.

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": "industry_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
certNoRSSD id of a bank for that bank's full terminal view, or empty / 'all' for the industry aggregate. UBPR peer ranks require Pro; ML risk fields require a free-or-above account (null otherwise).
peerNoRender as a peer-group aggregate instead of one bank: 'tier:<1-6>' (asset tier) or 'state:<XX>'. Takes precedence over `cert`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-annotation context — upstream sources (FFIEC + FDIC + FRED) and unit conventions (whole dollars, not thousands; ratios as percentages) — which prevents misreading returned numbers. It stops short of describing payload size, entitlement behavior, or what happens when fields are null.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no filler; the unit convention is stated before the agent needs it. The first sentence is somewhat redundant with the title, which keeps it from a 5.

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?

There is no output schema, so the description carries the full burden of explaining what comes back from a self-described "composite" payload — yet it never enumerates the sections, metrics, or shape of the response. The parameters are well covered by the schema, but an agent cannot anticipate the return value at all, which is a significant gap for a dashboard aggregator.

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?

Schema description coverage is 100% and the two parameters are documented richly in the schema, including enum-like forms ('tier:<1-6>', 'state:<XX>'), the empty/'all' convention, and the precedence rule for `peer`. The description itself adds nothing about parameters, so the baseline of 3 is warranted rather than higher.

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

Purpose3/5

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

"Composite industry terminal dashboard payload" conveys that this returns an aggregated industry-level dataset and names its upstream sources, but it largely restates the tool name (industry_dashboard) and never states what the payload actually contains (which metrics, sections, or time series). It also gives no differentiation from siblings such as industry, risk_dashboard, or failures_dashboard, so an agent cannot tell from the description which dashboard to pick.

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 when-to-use or when-not-to-use guidance and no named alternative. The only selection hints (empty/'all' for the industry aggregate, peer precedence over cert) live in the parameter descriptions rather than in the tool description, and nothing tells the agent why it would choose this dashboard over the other industry_* tools.

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