Unified Jobs MCP Server

get_premium_access

Returns paid x402 endpoint details for normalized cross-ATS compensation and per-company hiring-intent signals, including URL, USD price, and payment parameters.

Instructions

Describe the metered depth endpoints available beyond this free server: a normalized cross-ATS compensation layer and a per-company hiring-intent signal. These are served pay-per-call over x402 (USDC on Base, no account/API key — the caller's wallet pays the 402 inline). Returns the base URL, each endpoint's path + USD price + what it adds, and the exact payment parameters. No network call, no payment.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well by explicitly stating 'No network call, no payment.' It also clarifies that the payment mechanism belongs to the premium endpoints, not to this call, which prevents misinterpreting it as a paid or networked action.

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 definition is front-loaded with the core purpose and then adds useful payment and return details. It is somewhat dense but every sentence contributes relevant information for this zero-parameter metadata tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 appropriately explains what is returned: base URL, endpoint paths, USD prices, value added, and exact payment parameters. It also clarifies the no-side-effect behavior, making the definition complete for invocation.

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?

The tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics and correctly focuses on return contents instead.

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 uses a specific verb and resource: 'Describe the metered depth endpoints available beyond this free server.' It names the premium capabilities and clearly distinguishes this metadata tool from the sibling search/list tools, which target actual data retrieval.

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?

It gives clear context for use: discovering endpoints beyond the free server, including their pricing and payment parameters. It does not explicitly state when not to call it or name sibling alternatives, but the purpose is sufficiently clear for selection.

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

Deploy Server