Skip to main content
Glama

Get comp and premium benchmarks

get_benchmarks
Read-onlyIdempotent

Broker comp-rate benchmarks (median, 25th and 75th percentile of commissions + fees as a share of premium) and median premium per covered life per month, by line of coverage and group size.

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

Input Schema

NameRequiredDescriptionDefault
lineNoLine of coverage, e.g. Medical, Dental, Life. Omit for all lines.
participantsNoGroup size to pick the size band. Omit for all bands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description then adds real behavioral substance beyond them: the exact statistic definitions (median with 25th/75th percentiles), what is measured (commissions + fees as a share of premium, premium per covered life per month), and the grouping granularity. It stops short of stating units, sample-size caveats, or how many rows come back per line/size band.

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?

It is a single dense sentence with no filler, front-loading the two headline metrics and trailing with the grouping dimensions. The nested parentheses make it slightly harder to parse than a short bulleted breakdown would be, but nothing is wasted.

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 2-optional-parameter read tool with no output schema, the description effectively serves as the return-value documentation by enumerating the metrics produced. Remaining minor gaps are units (percent vs. basis points) and whether multiple rows are returned when both filters are omitted, which an agent would want before formatting results.

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%, including the example line values and the 'omit for all' behavior, so the schema already carries the parameter meaning. The description only echoes that both dimensions are grouping keys ('by line of coverage and group size'), adding marginal interpretation such as 'size band' bucketing already described in the schema. 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?

The description names the exact resource and metrics: broker comp-rate benchmarks (median, 25th and 75th percentile of commissions + fees as a share of premium) plus median premium per covered life per month. That is far more specific than a bare 'get benchmarks', and its subject matter is plainly distinct from the entity lookups in the sibling set, though it never explicitly contrasts itself 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 Guidelines2/5

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

There is no when-to-use guidance, no statement of when not to use it, and no naming of an alternative. The only implied usage cue is the schema's 'Omit for all lines/all bands', which is not repeated in the description, so an agent must infer the call context entirely.

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