Skip to main content
Glama

Get broker book of business

get_broker
Read-onlyIdempotent

A brokerage firm's book from Form 5500 filings: employers, participants, premium placed, commissions and fees, comp rate, top states and carriers, group sizes, recent broker-of-record changes (groups gained and groups that moved), largest employers. Firms with 5+ employers only; individual agents aren't covered.

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": {
      "name": "<name>"
    },
    "name": "get_broker"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFirm name or page slug, e.g. Lockton or marsh-mclennan-agency

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful data-scope context beyond that: the source (Form 5500 filings), the 5+ employer coverage threshold, and the exclusion of individual agents. It does not state filing-year currency, pagination, or what happens for an unknown firm name.

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?

One dense, front-loaded sentence whose clause list is all substantive content describing the returned book. The enumeration is long but each item earns its place; it could be broken into scope and contents for faster scanning.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of describing return values, and it does so thoroughly: employers, participants, premium, commissions and fees, comp rate, states, carriers, group sizes, broker-of-record changes, and largest employers. Combined with the stated coverage limits, an agent has enough to decide and call correctly.

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 schema already documents the single parameter with examples ('Lockton or marsh-mclennan-agency'), so baseline is 3. The description adds only an implicit clarification that the name refers to a firm rather than a person, via the agent-exclusion sentence.

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 resource ('A brokerage firm's book from Form 5500 filings') and enumerates its contents, which clearly separates it from get_employer, get_carrier, get_state and search_employers. It lacks an explicit verb like 'retrieve' or 'summarize', so the action is implied rather than stated, but the scope is unmistakable.

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

Usage Guidelines4/5

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

Eligibility exclusions are explicit: 'Firms with 5+ employers only; individual agents aren't covered,' which tells the agent when this tool will return nothing useful. It stops short of naming a fallback tool for smaller firms or individual agents, so there is no alternative-routing guidance.

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