Skip to main content
Glama

Bank Securities Trends

securities_trends
Read-only

Quarterly AFS/HTM portfolio with industry-wide overlay. (Source: FFIEC Call Report (Schedule RC-B).) Dollar amounts are in thousands of US dollars ($000s); ratios are percentages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rssd_id": "<rssd_id>"
    },
    "name": "securities_trends"
  }
}

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.
quartersNoNumber of bank quarters (1-80, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 useful context about the data source, quarterly frequency, and units ($000s, percentages), but it does not explain what 'industry-wide overlay' means operationally or what the response structure looks like.

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?

The description is three compact sentences with no wasted wording. It front-loads the dataset definition, then names the source and units, so every sentence earns its place.

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

Completeness3/5

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

For a simple two-parameter read tool with no output schema, the description gives the dataset, source, and units but leaves the return content underspecified. It does not say which securities metrics or trend comparisons are returned, and 'industry-wide overlay' remains ambiguous.

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 both rssd_id and quarters are documented in the schema. The description adds no parameter-specific meaning beyond the schema; it only clarifies output units, so the baseline of 3 is appropriate.

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 identifies a specific dataset: a quarterly AFS/HTM portfolio with an industry-wide overlay, sourced from FFIEC Call Report Schedule RC-B. It is clear what data the tool returns, but it does not explicitly distinguish itself from sibling tools such as industry_securities_trends or securities.

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?

The description provides no when-to-use guidance, no exclusions, and no explicit alternatives. An agent must infer from the name and the phrase 'industry-wide overlay' whether this is the right tool versus industry_securities_trends or a broader bank trends tool.

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