Skip to main content
Glama
Sign In
Grey Ridge Jobs MCP

Grey Ridge Jobs MCP

by rezearcher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_premium_access

Returns pay-per-call endpoint details for deeper hiring data beyond the free tier: cross-ATS compensation, company hiring intent, high-volume multi-ATS search, USD prices, and x402 payment parameters.

Instructions

Describe the metered depth endpoints available beyond this free server: a normalized cross-ATS compensation layer, a per-company hiring-intent signal, and a hosted high-volume multi-ATS search. 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 (network, asset, pay-to, handshake). 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains the x402 pay-per-call model (USDC on Base, wallet pays the 402 inline, no account/API key) and explicitly states 'no network call, no payment' for this invocation. The only gap is that it doesn't clarify that the returned payment parameters are informational rather than triggering a charge.

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?

Three sentences, front-loaded with the purpose, then the pricing model, then the return shape. Dense but each sentence carries distinct information; the x402 parenthetical is slightly heavy but earns its place by pre-empting 'do I need an API key?' questions.

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 must explain returns — and it does precisely: base URL, per-endpoint path + USD price + what it adds, and the exact payment parameters (network, asset, pay-to, handshake). An agent has everything needed to call it and interpret the response.

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?

Zero parameters, so per the baseline this scores 4. There is nothing parameter-wise to document and the description correctly does not invent any.

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 a specific action (describe/discover metered paid endpoints) and enumerates the three resources it covers (compensation layer, hiring-intent signal, high-volume multi-ATS search). This clearly separates it from the free-server siblings, though it never names those siblings directly.

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 phrase 'beyond this free server' implies the trigger — reach for this when the free tools are insufficient — but usage is left to inference. There is no explicit 'use this when X' or 'do not use this for Y' guidance relative to search_jobs or list_platforms.

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

Deploy Server

Other Tools