AgentX x402 Services (paid MCP tools)

search_ats_jobs

Read-onlyIdempotent

Open jobs from a public Greenhouse or Lever board with query/location/department filters. GET /x402/ats-jobs?platform=&company= — $0.01.

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": {
      "platform": "<platform>",
      "company": "<company>"
    },
    "name": "search_ats_jobs"
  }
}

Input Schema

Name	Required	Description
`limit`	No	1-50
`query`	No
`company`	Yes	Board slug, e.g. coinbase
`payment`	No	Optional. Your x402 payment proof for this exact call — the PAYMENT-SIGNATURE value produced by settling this route's 402 challenge (USDC on Base, Polygon or Solana), or an MPP 'Authorization: Payment ...' value. Omit on a first call: the tool then returns the live 402 challenge to pay against. This server relays your proof upstream and retries; it never creates or settles payments itself.
`location`	No
`platform`	Yes	greenhouse or lever
`department`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / payment / description

Previous value: -"Optional. Your x402 payment proof for this exact call — the PAYMENT-SIGNATURE value produced by settling this route's 402 challenge (USDC on Base or Solana), or an MPP 'Authorization: Payment ...' value. Omit on a first call: the tool then returns the live 402 challenge to pay against. This server relays your proof upstream and retries; it never creates or settles payments itself."New value: +"Optional. Your x402 payment proof for this exact call — the PAYMENT-SIGNATURE value produced by settling this route's 402 challenge (USDC on Base, Polygon or Solana), or an MPP 'Authorization: Payment ...' value. Omit on a first call: the tool then returns the live 402 challenge to pay against. This server relays your proof upstream and retries; it never creates or settles payments itself."

AddedNov 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds two genuine traits beyond that: results are limited to public boards, and the call costs $0.01. It omits the 402-challenge/retry behavior of the call, though the payment parameter's schema text covers that in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the capability and filters, followed by the concrete route and price. No filler and nothing an agent has to parse through to reach the operative information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say what a job record contains or how results are shaped, and it does not. It also omits that a first call without a payment proof returns a 402 challenge — a behavior the agent must anticipate — although that is fully spelled out in the payment parameter description.

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?

At 57% schema coverage the description does useful work: it maps query, location and department to filter semantics and ties platform/company to the endpoint template, including that company is a board slug. It says nothing about limit or payment, but those two carry their own schema descriptions.

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?

The description names a specific verb and resource ('Open jobs from a public Greenhouse or Lever board') plus the filter dimensions, so an agent can tell this is a listing/search tool. It does not explicitly distinguish itself from the sibling get_ats_job_detail, leaving the list-vs-detail boundary to be inferred from the name.

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 implied by 'with query/location/department filters' and the required platform/company pair, which signals a board-scoped search. There is no explicit when-to-use, no when-not-to-use, and no pointer to get_ats_job_detail for single-job retrieval.

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

All AgentX x402 Services (paid MCP tools) 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?