Skip to main content
Glama

SEC Peer Group

sec_peers
Read-only

SEC-derived peer-group assignment for this bank's registrant(s) - SIC industry, asset tier, exchange listing, and latest reported total assets. (Source: SEC EDGAR (company facts + SIC).)

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

Input Schema

NameRequiredDescriptionDefault
rssd_idYesFederal Reserve RSSD id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 genuine context by naming the upstream data source (SEC EDGAR company facts + SIC), which tells the agent where the classification comes from, but says nothing about return shape, coverage gaps, or whether multiple registrants are returned.

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 purpose, followed by the returned dimensions and a parenthetical provenance note. No filler or redundancy.

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?

With no output schema, the description usefully lists what the peer assignment contains, which is enough to decide relevance. The unresolved plural "registrant(s)" leaves mild ambiguity about result cardinality for banks with multiple SEC registrants.

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% with a single documented rssd_id parameter, so the schema carries the semantics. The description adds no formatting, range, or validity detail beyond it, which is the expected baseline here.

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?

States a specific resource (SEC-derived peer-group assignment) and enumerates the dimensions it covers: SIC industry, asset tier, exchange listing, and latest reported total assets. The qualifier "SEC-derived" and the EDGAR source note weakly separate it from generic siblings like peers or peer_groups, but it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the SEC/EDGAR framing signals 'use this when you want the regulatory-filing-based peer set.' There is no statement of when to prefer it over peers or peer_groups, no prerequisites, and no exclusions.

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