Skip to main content
Glama

Salary Histogram

salary_histogram
Read-onlyIdempotent

"What does [role] pay" / "salary distribution for [job]" / "average salary for [title] in [location]" / "wage histogram for [profession]", wage distribution histogram for jobs matching a query. Use for salary benchmarking, comp negotiation research, market-rate analysis.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "what": "data scientist",
      "country": "gb",
      "location_filter": "London"
    },
    "name": "salary_histogram"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatNo
whereNo
countryYes
location_filterNoAdzuna location id (e.g. "London")

Output Schema

NameRequiredDescriptionDefault
currencyNoSalary currency
histogramNoSalary distribution buckets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "country": "gb",
      +    "location_filter": "London",
      +    "what": "data scientist"
      +  },
      +  {
      +    "country": "ca",
      +    "what": "nurse",
      +    "where": "Toronto"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "currency": {
      +      "description": "Salary currency",
      +      "type": "string"
      +    },
      +    "histogram": {
      +      "description": "Salary distribution buckets",
      +      "items": {
      +        "properties": {
      +          "count": {
      +            "description": "Jobs in this salary range",
      +            "type": "number"
      +          },
      +          "max_salary": {
      +            "description": "Bucket upper bound",
      +            "type": "number"
      +          },
      +          "min_salary": {
      +            "description": "Bucket lower bound",
      +            "type": "number"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond annotations — no coverage about which markets/countries are supported, result bucketing, or sample-size caveats for sparse queries, which matters for a distribution tool with open-world data.

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?

Front-loaded with the user-phrasings that route an agent to it, then a single declarative sentence of purpose plus a short use-case list. The quoted query-string pile-up is slightly noisy but each phrase serves as a routing cue; nothing is padded prose.

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 an output schema present, return-value explanation is unnecessary, and the read-only annotations remove the safety burden. The remaining gap is the ambiguity between the two location parameters and any note on data coverage, but for a 4-parameter read-only lookup the description is sufficient to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% (only location_filter is documented), so the description carries real weight by explaining that 'what' is the role/job/title text, 'where'/'location_filter' is the location, and by seeding the '[title] in [location]' pattern. This adds meaning beyond the bare schema, though it still doesn't explicitly contrast 'where' vs 'location_filter'.

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?

States a specific verb and resource — 'wage distribution histogram for jobs matching a query' — and the lead-in strings map colloquial salary questions ('what does [role] pay', 'average salary for [title] in [location]') onto the tool. An agent can tell this apart from adzuna_search because the output is explicitly a distribution histogram rather than listings.

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?

Gives concrete usage contexts: salary benchmarking, comp negotiation research, market-rate analysis, and lists the query phrasings that should route here. It does not name an explicit alternative or state when NOT to use it (e.g. no guidance on choosing this over a general job search), so it stops short of full 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.