Skip to main content
Glama

Get employer details

get_employer
Read-onlyIdempotent

One employer by EIN: every Schedule A contract (carrier, lines, premium, covered lives, commissions and fees, comp rate, broker), plans with links to the original filing PDFs, and plan-year history back to 2019 (participants, premium, funding, carriers, brokers).

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

Input Schema

NameRequiredDescriptionDefault
einYes9-digit EIN (dashes optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety bar is low. The description adds genuinely non-structured context: the scope boundary 'plan-year history back to 2019' and the fact that plans link back to original filing PDFs. It does not state what happens for an unknown or malformed EIN.

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?

A single front-loaded sentence leads with the scope ('One employer by EIN') then enumerates return contents. The long parenthetical lists are dense but every item earns its place by telling the caller what data will come back where no output schema exists.

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?

Because there is no output schema, the description must and does characterize the return payload in detail, including the temporal cutoff. The remaining gap is failure behavior for EINs with no record, which matters for a lookup keyed on a single identifier.

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?

With a single parameter at 100% schema description coverage, the schema already carries the format ('9-digit EIN (dashes optional)'). The description only restates 'by EIN' and adds that exactly one employer is returned, which is not parameter-level meaning. Baseline 3 applies.

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 verb+resource ('One employer by EIN') and enumerates the payload domains (Schedule A contracts, plans, plan-year history), which implicitly separates it from the multi-result sibling search_employers. It never names the alternative, so sibling differentiation is inferred rather than stated.

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 implied by 'One employer by EIN' - you use it when you already have an EIN and want one entity's full record. There is no explicit when-to-use/when-not guidance and no pointer to search_employers for the case where the caller does not yet have an EIN.

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