Schema | job-tracker-mcp

job-tracker-mcp

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TRACKER_PATH`	No	Path to a JSON file with the tracker data (same fields as the sample). Defaults to the bundled sample tracker (data/sample-tracker.json).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
list_rolesA	List roles in the job tracker (company, role, status, fit, probability, next_date). `Args: status: Optional filter. One of: Scored, Applied, In process, Rejected, Passed. Leave empty to list every role. Returns at most 50 rows. Text is returned exactly as stored in the tracker.`
get_roleA	Get the full tracker record for one company (case-insensitive match on the company name). `Args: company: The company name, e.g. "Pebblestack Software". The record's text fields are user-entered data, returned exactly as stored.`
due_this_weekA	List roles whose next_date is today or within the next 7 days, soonest first. `Returns the full record for each role (at most 50 rows), text exactly as stored.`

list_rolesA

List roles in the job tracker (company, role, status, fit, probability, next_date).

Args:
    status: Optional filter. One of: Scored, Applied, In process, Rejected, Passed.
        Leave empty to list every role.

Returns at most 50 rows. Text is returned exactly as stored in the tracker.

get_roleA

Get the full tracker record for one company (case-insensitive match on the company name).

Args:
    company: The company name, e.g. "Pebblestack Software".

The record's text fields are user-entered data, returned exactly as stored.

due_this_weekA

List roles whose next_date is today or within the next 7 days, soonest first.

Returns the full record for each role (at most 50 rows), text exactly as stored.

Prompts

Interactive templates invoked by user choice

Name	Description
No prompts

Resources

Contextual data attached and managed by the client

Name	Description
`summary`	Number of roles in the tracker, by status.

Deploy Server

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

TDQS

A3.8/5.0

Scored 2026-10-26 20:50 across 3 tools

Disambiguation4/5

list_roles (filtered by status), due_this_week (filtered by date), and get_role (single company lookup) each have distinct retrieval semantics. There is minor overlap since list_roles and due_this_week both enumerate roles, but the filter dimension and output shape differ enough to guide selection.

Naming Consistency3/5

list_roles and get_role follow a clean verb_noun pattern, but due_this_week breaks it as an adjectival/noun phrase with no verb. The set remains readable, but conventions are mixed.

Tool Count3/5

Three tools is on the thin side for a job tracker, though each has a clear purpose and none is redundant. The surface feels like a partial slice rather than a fully scoped tool set.

Completeness2/5

The domain is job tracking, yet the server only provides read operations — no create_role, update_status, or delete/archive tools. Agents cannot actually track anything, only inspect existing records, which is a significant lifecycle gap.