Skip to main content
Glama

Community Bank Derivatives

community_bank_derivatives
Read-onlyIdempotent

Derivatives reported by FFIEC 051 filers (banks under 5 billion dollars), quarterly. (Source: OCC Report on Bank Trading and Derivatives Activities.)

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

Input Schema

NameRequiredDescriptionDefault
periodNoLatest quarter shown, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered without the description. The description adds the data source (OCC Report on Bank Trading and Derivatives Activities) and the filer population, which is genuinely useful context, but says nothing about return shape, units, or how the period argument affects results.

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?

One sentence, front-loaded with the resource and its scope, followed by a compact source attribution. No filler or repetition.

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 single-parameter, read-only dataset tool with full schema coverage and complete annotations, the description supplies the scope, cadence, and provenance an agent needs. Minor gaps remain around what happens when the period is omitted and what the response contains.

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 single period parameter is documented in the schema as a YYYY-MM-DD latest-quarter date. The description adds the word 'quarterly', clarifying the reporting cadence behind that parameter, but offers no additional format or default behavior detail.

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 dataset (derivatives) and precisely bounds it: FFIEC 051 filers under $5B, quarterly. That is enough for an agent to know exactly what is returned, though it never states a verb and does not distinguish itself from sibling tools like bank or credit_quality.

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 statement of when to use this tool versus alternatives, no exclusions, and no note about whether the data covers only community banks versus all filers beyond the implicit '$5B' scope. The agent must infer usage purely from the dataset 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