CareerHolo

Typical pay for a role

salary_for

Read-onlyIdempotent

The median and typical range of stated pay for a tech role in a place, from open postings, in US dollars a year. Roles: Software, Backend, Frontend, Full Stack, Data, DevOps, Site Reliability, Machine Learning, Mobile, iOS, Android and Security Engineer, Data Scientist, Data Analyst, Product Manager, Engineering Manager, Technical Program Manager, UX Designer, UI Designer, Solutions Architect. Places: Remote, United States, UK, Germany, Netherlands, Canada, India, San Francisco, New York, London, Berlin, Amsterdam, Toronto, Bangalore.

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": {
      "role": "<role>",
      "place": "<place>"
    },
    "name": "salary_for"
  }
}

Input Schema

Name	Required	Description	Default
`role`	Yes	e.g. "Backend Engineer"
`place`	Yes	e.g. "Germany" or "Remote"

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description adds real value: the figures are 'stated pay' from 'open postings' (not official statistics), reported as a median plus a typical range, denominated in USD per year — all facts an agent cannot get from annotations.

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?

The core definition is front-loaded in one tight sentence, followed by two long enumerations that are dense but necessary given the absence of enum constraints. No filler sentences, though the value lists dominate the text.

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?

There is no output schema, so the description must carry the return shape — and it does, specifying median plus typical range in USD/year from posting data. Remaining gaps are modest: no note on data recency, sample size, or fallback behavior for unsupported role/place combinations.

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

Parameters4/5

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

With 100% schema coverage but zero enums, the enumerated role and place lists are the main safeguard against invalid calls, which is a genuine addition beyond the schema's bare examples. It still doesn't say whether matching is exact or case-insensitive, or what happens for a role/place outside the lists.

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 first sentence names a specific metric (median and typical range of stated pay), the object (a tech role in a place), the data source (open postings) and the unit (USD per year). An agent can immediately tell this apart from search_jobs or company_jobs, which deal with listings rather than aggregate pay.

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?

Usage is only implied: the description makes clear this is a pay-lookup, but never says when to choose it over siblings like company_jobs or search_jobs, nor any preconditions. The enumerations constrain inputs rather than explain when to invoke the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CareerHolo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?