Skip to main content
Glama

Industry Trends

industry_trends
Read-onlyIdempotent

Industry-wide metric trends over time. (Source: BankRegReports.)

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

Input Schema

NameRequiredDescriptionDefault
quartersNoNumber of recent quarters (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only a source attribution ('BankRegReports') and does not disclose which metrics are aggregated, how they are aggregated across institutions, or what the time granularity looks like beyond the quarters parameter.

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 sentences with the resource and source front-loaded and no wasted wording. The brevity is appropriate in form, though the content is thin rather than padded.

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 and the tool sits in a dense cluster of similarly named industry and trend tools, so the description should identify the metrics covered and how results differ from those siblings. It leaves the agent unable to predict the response contents, which is a meaningful gap for a data-retrieval tool.

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 coverage is 100% and the single optional 'quarters' parameter is fully documented with a default in the schema, so a baseline of 3 applies. The description adds no further meaning about how the quarter window interacts with data availability or reporting lag.

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?

States the resource ('industry-wide metric trends') and temporal scope ('over time'), which loosely distinguishes it from bank-level siblings like bank_trends. However, 'metric' is undefined, so an agent cannot tell what this returns versus industry_securities_trends, industry_cu_ratios, or industry_macro, which also sound like industry-level trend tools.

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 use this versus the many sibling trend tools, and no prerequisites or exclusions are mentioned. The only usage-relevant hint is the default of 20 quarters, which comes from the schema, not the description.

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