Skip to main content
Glama
Sign In
Unified Jobs MCP Server

Unified Jobs MCP Server

by rezearcher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_sources

Lists the job sources merged by the server, ATS company addressing, and cross-source deduplication/merge behavior. Shows how canonical jobs are formed without a network call.

Instructions

List the job sources this server merges across, how to address ATS companies, and how the cross-source dedup/merge behaves (canonical key, field union, degrade-open). No network call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.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 disclose real behavioral traits: no network call (local/safe/instant), and how cross-source merging behaves (canonical key, field union, degrade-open). This meaningfully informs the agent about how data returned by the sibling search tools is composed. It does not say whether what it returns is static or reflects live configuration, but the disclosure is well above average.

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?

A single front-loaded sentence with no waste; the key constraint (no network call) is placed last as a compact qualifier. Dense but every clause carries information an agent would otherwise have to infer.

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 zero-parameter, no-output-schema tool, the description covers what the tool surfaces (sources, ATS addressing rules, dedup behavior) and its cost profile (no network call). The only gap is that it doesn't sketch the response shape at all, which leaves some ambiguity about how the 'how to address ATS companies' information is presented.

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 means the baseline is 4. The mention of 'how to address ATS companies' adds value beyond the empty schema by hinting at how source identifiers map into the sibling search calls.

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 verb and resource ('list the job sources this server merges across') and adds the scope of the returned content (ATS addressing, dedup/merge semantics). It does not explicitly contrast itself with search_unified_jobs or search_hn_hiring, but the nature of the operation (metadata listing vs. search) makes the distinction reasonably evident.

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 'No network call' note implies a cheap, local, safe-to-call-anytime tool, and the content described implies it's for learning about sources before searching. However, the description never states when to prefer this over the sibling search tools or what prerequisites exist — usage is only implied.

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