Skip to main content
Glama

Finder Jobs

Salary statistics

salary_stats
Read-onlyIdempotent

Salary statistics (25th/50th/75th percentile, sample size) from active vacancies on Finder. country: ISO code; profession: name in local language (e.g. 'Бухгалтер', 'Programmierer'); empty = all jobs; city optional. Returns the matching Finder salary page url when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoOptional city name as written locally
countryYesCountry ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id
professionNoProfession in local language, e.g. 'Бухгалтер', 'Programmierer'. Empty = all jobs

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
p25No
p75No
urlNo
cityNo
meanNo
errorNo
medianNo
periodNo
sourceNo
countryNo
currencyNo
professionNo
sample_sizeNo
range_1sigmaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"Optional city name as written locally"
    • addedInput schema / properties / country / description
      Added value: +"Country ISO code: ru (Russia, finder.work), by, kz, kg, de, fr, be, ch, se, id"
    • addedInput schema / properties / profession / description
      Added value: +"Profession in local language, e.g. 'Бухгалтер', 'Programmierer'. Empty = all jobs"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "city": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "City"
      +    },
      +    "country": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Country"
      +    },
      +    "currency": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Currency"
      +    },
      +    "error": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Error"
      +    },
      +    "mean": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Mean"
      +    },
      +    "median": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Median"
      +    },
      +    "p25": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "P25"
      +    },
      +    "p75": {
      +      "anyOf": [
      +        {
      +          "type": "number"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "P75"
      +    },
      +    "period": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Period"
      +    },
      +    "profession": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Profession"
      +    },
      +    "range_1sigma": {
      +      "anyOf": [
      +        {
      +          "items": {
      +            "type": "number"
      +          },
      +          "type": "array"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Range 1Sigma"
      +    },
      +    "sample_size": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Sample Size"
      +    },
      +    "source": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Source"
      +    },
      +    "url": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Url"
      +    }
      +  },
      +  "title": "SalaryStats",
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/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=false, so the safety profile is covered. The description adds that statistics come only from active vacancies and that a Finder salary page URL is returned when available, which is useful but modest added context.

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?

Compact and front-loaded: the returned metrics and source lead the sentence, with parameter hints trailing. A couple of clauses duplicate schema text, but there is little waste overall.

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 and annotations covering the read-only/idempotent profile, the description need not explain return values; noting the conditional salary-page URL suffices. For a 3-parameter read tool it is essentially complete, though sibling routing remains 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 description coverage is 100%, so the schema already documents country ISO codes, local-language profession names, and the optional city. The description largely restates these semantics ('country: ISO code', 'profession: name in local language', 'empty = all jobs') without adding format or edge-case detail beyond the schema.

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 the specific resource and metric set (25th/50th/75th percentile, sample size) and the source population (active vacancies on Finder), which is precise enough for an agent to know what it retrieves. It does not explicitly differentiate itself from siblings like search_vacancies or get_vacancy, so it stops short of a 5.

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?

The description implies the use case (aggregate salary data for a country/profession) and gives filling guidance ('empty = all jobs', 'city optional'), but never states when to choose this over search_vacancies or get_vacancy. Usage is inferred rather than instructed.

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