Skip to main content
Glama

getwork.dev

Salary insights

salary_insights
Read-onlyIdempotent

What employers publish as pay for jobs matching the same filters as search_jobs: yearly p25 / median / p75 per currency, with sample sizes. Use it for 'what does X earn' or 'is this offer fair'; it lists no jobs. Figures come from published ranges in live job ads, not surveys.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFree text, e.g. 'distributed systems' or 'payments'. Every word must match (a word also matches its synonyms).
stackNoTechnology tags that must all be in the role's primary stack (any one of them with stack_any), lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match.
remoteNo
companyNoCompany slug from list_companies.
excludeNoLeave out jobs matching any of these: a stack tag (not in the primary stack or title), a role family, or a topic like 'crypto' or 'gambling' (not mentioned anywhere, synonyms included).
regionsNoAny of these regions. Worldwide-remote jobs are always included.
currencyNoISO currency code (EUR, USD, GBP). Restricts to jobs that publish pay in this currency.
countriesNoISO 3166-1 alpha-2 codes, e.g. NL, DE, GB. Common country names (Netherlands, UK) are read too.
seniorityNo
stack_anyNoAny one of the stack tags will do instead of all of them: 'Go or Rust'.
role_familyNo
posted_within_daysNo

Output Schema

NameRequiredDescriptionDefault
noteNo
periodNo
by_currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / countries / description
      Previous value: -"ISO 3166-1 alpha-2 codes, e.g. NL, DE, GB."New value: +"ISO 3166-1 alpha-2 codes, e.g. NL, DE, GB. Common country names (Netherlands, UK) are read too."
  2. Changed2 schema fields changed
    • changedInput schema / properties / stack / description
      Previous value: -"Technology tags that must all be in the role's primary stack, lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match."New value: +"Technology tags that must all be in the role's primary stack (any one of them with stack_any), lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match."
    • addedInput schema / properties / stack_any
      Added value: +{
      +  "default": false,
      +  "description": "Any one of the stack tags will do instead of all of them: 'Go or Rust'.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered. The description still adds real context beyond that: the provenance of the numbers ('published ranges in live job ads, not surveys') and the presence of sample sizes, which tells the agent how much to trust thin results. It stops short of saying what happens with zero matches or small samples.

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?

Two sentences, front-loaded with the returned statistic and its grain, then the disambiguation, then the data-provenance caveat. No sentence is padding.

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, the description doesn't need to describe return values, and it covers purpose, filter lineage and data trustworthiness for a 12-parameter, zero-required tool. Only thin-data or empty-result behavior is left unaddressed.

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 67%, so most parameters are already documented. The description's main added semantic is that filters behave identically to search_jobs, which lets an agent transfer its mental model; it adds nothing further about individual fields like currency or posted_within_days.

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 ('what employers publish as pay for jobs') plus the exact shape of the output (yearly p25/median/p75 per currency, with sample sizes). It explicitly separates itself from the sibling that could be confused with it: 'it lists no jobs', versus search_jobs which does.

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 use cases ('what does X earn', 'is this offer fair') and points to search_jobs as the filter source and implicit alternative. It doesn't spell out when-not-to-use beyond 'it lists no jobs', but that single clause plus the filter-sharing statement is clear 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