Skip to main content
Glama

Dental associate salary benchmarks by state

dental_salary_benchmarks
Read-onlyIdempotent

Returns dental associate compensation benchmarks for a US state, computed from recent job listings: average and median base salary, daily rate, production percentage, signing bonuses, and how often listings include health insurance, 401(k), or paid malpractice. Figures are omitted when the sample is too small. Relevant when a dentist asks what associates are paid in a state or how pay is usually structured there.

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

Input Schema

NameRequiredDescriptionDefault
stateYesUS state as a 2-letter postal code (e.g. TX, CA, DC). Full state names are also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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=false, so the safety profile is known. The description adds two genuinely useful facts beyond that: figures are derived from recent job listings, and fields are omitted when the sample is too small, which tells the agent to tolerate missing values. It does not specify the recency window, units/period for salary figures, or behavior for a state with no data at all.

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?

Three sentences, all front-loaded with the core capability first, then the return contents, then the usage trigger. Little waste, though the metric enumeration in sentence one partially overlaps with the benefits list and could be tightened.

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 correctly carries the burden of describing the return shape, listing the metrics and warning that figures may be omitted. What remains unstated is minor but real: the time window for 'recent' listings and the currency/period basis of the salary figures.

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 single 'state' parameter is already documented with a 2-letter postal code format and full-name fallback. The description only restates 'for a US state', adding no format, casing, or validity detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Returns dental associate compensation benchmarks for a US state.' It then enumerates the exact computed figures (average/median base salary, daily rate, production percentage, signing bonuses, benefits prevalence), which lets an agent distinguish it from search_dental_jobs (raw listings) or estimate_dental_malpractice without opening any schema.

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?

It states the triggering condition explicitly: 'Relevant when a dentist asks what associates are paid in a state or how pay is usually structured there.' That is a clear when-to-use signal, but it offers no exclusion or hand-off to a sibling when the user wants individual listings rather than aggregates.

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