SiteCheck Jobs & Property

US median pay for a job title from PayScale's public salary

jobs_payscale

Read-only

US median pay for a job title from PayScale's public salary research page: the title's compensation (USD, annual) and the related career-path roles with their pay. Pass the title as PayScale writes it in its URL, e.g. Software_Engineer. Figures are PayScale's published estimates. Related tools on this server, for a different need: jobs_indeed when you need Indeed job search: title, company, location, salary range; jobs_simplyhired when you need SimplyHired job search: title, company, location, salary. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "job": "<job>"
    },
    "name": "jobs_payscale"
  }
}

Input Schema

Name	Required	Description	Default
`job`	Yes	Job title as in the PayScale URL, e.g. Software_Engineer (letters, digits, underscores)

Output Schema

Name	Required	Description	Default
`job`	No
`source`	No
`currency`	No
`isHourly`	No
`checkedAt`	No
`reviewCount`	No
`compensation`	No
`relatedRoles`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new context: the cost is $0.002 USDC per successful call via x402 on Base, Solana or Arc, and failed calls are not charged. It also states the figures are PayScale's published estimates and that results include related career-path roles, though it says nothing about failure modes such as an unmatched title.

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 purpose and input format are front-loaded in the first two sentences, and the sibling/pricing notes follow. The sentence enumerating sibling tools and their fields is somewhat verbose, but every element still carries routing or billing information.

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?

For a one-parameter read tool with an output schema, the description covers what it returns, input format, cost and sibling alternatives. Remaining gaps (behavior on unknown titles, response latency) are minor given the output schema documents the return shape.

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% and the single 'job' parameter is already documented as a PayScale-URL-style title with the Software_Engineer example. The description restates the same convention rather than adding new meaning, so the baseline of 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 names a specific verb and resource: median US pay for a job title from PayScale's public salary research page, returning annual USD compensation plus related career-path roles. That is clearly distinct from the job-board siblings that return listings rather than pay data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent: use jobs_indeed for Indeed job search (title, company, location, salary range) and jobs_simplyhired for SimplyHired job search, implicitly leaving payscale for pay-figure lookups. It also gives the required input convention (title as written in the PayScale URL, e.g. Software_Engineer).

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

All SiteCheck Jobs & Property 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?