Skip to main content
Glama

BankRegReports

Industry Snapshot

industry
Read-only

Industry-wide aggregate snapshot. (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"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/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 by structured data rather than the description. Beyond that, the description adds only the source (BankRegReports) and nothing about what the aggregate covers, its granularity, time basis, or size of the payload. For a no-parameter snapshot tool with many overlapping siblings, that is thin added context.

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 no filler or redundancy, and the core purpose is front-loaded. The brevity is appropriate in form, though it shades into under-specification rather than crispness, and the parenthetical source is of marginal decision value.

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?

With no output schema, no parameters, and a dense sibling set of industry_* tools, the description carries the full burden of explaining what the snapshot actually contains and when it applies. It supplies neither, leaving the agent unable to predict the response contents or choose confidently among alternatives.

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 for the description to supply; the baseline for a parameterless tool applies. The description does not need to compensate for any schema gap here.

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?

"Industry-wide aggregate snapshot" states a resource and a scope (industry-wide, aggregated), so the agent knows roughly what kind of data comes back. But it does not distinguish this from close siblings like industry_benchmarks, industry_dashboard, or industry_trends, all of which are plausibly also industry-wide aggregates. Purpose is recognizable but not differentiating.

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 guidance at all: no conditions, no exclusions, no mention of when an agent should pick this over industry_benchmarks or industry_dashboard. The only hint of context is the source attribution, which does not help selection. The agent must infer usage purely from the name.

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