Skip to main content
Glama
vinayvobbili

jobwatch

by vinayvobbili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_digest

Returns new jobs matching watchlist filters, ranked by fit score and keyword relevance, with known contacts per company. Use after fetch_jobs to view today's matches and application pace.

Instructions

New jobs that pass the watchlist's filters, best first (fit score when scored, then keyword relevance), with people the user knows at each company. Call fetch_jobs first to pick up today's postings. This is for finding jobs to consider; for jobs already queued use list_queued_jobs, and for applications use list_applications. total is how many matched before the limit (jobs left out stay new for the next digest). not_scored, when set, says why a job is never fit-scored (a Hacker News post listing several roles). pace, unless the user turned it off: applications sent today against how many they aim for a day (daily) and the most (max); once met, suggest the rest wait for tomorrow, but never refuse to help.

Input Schema

NameRequiredDescriptionDefault
limitNoThe most jobs to return, best first. Default: the watchlist's display.today (10 unless set; 25 when it's 0, for every match).
score_topNoHow many of the most relevant unscored jobs to fit-score against the resume with shortlist-ai first. 0 (the default) skips scoring; each job takes minutes on the local backend, so keep it small.
mark_shownNoMark the returned jobs as shown, so the next digest leaves them out. False to peek without changing anything.
include_seenNoAlso include jobs already shown in an earlier digest, not just new ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / limit / default
      Previous value: -25New value: +null
    • changedInput schema / properties / limit / description
      Previous value: -"The most jobs to return, best first."New value: +"The most jobs to return, best first. Default: the watchlist's display.today (10 unless set; 25 when it's 0, for every match)."
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
  2. Addedv0.3.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare non-read-only, open-world, non-idempotent, non-destructive; the description is consistent with these and adds substantive behavior beyond them: jobs left out stay new for the next digest, total counts matches before the limit, not_scored explains why a job is never scored, and the pace object's daily/max semantics. It does not state permissions or a return shape explicitly, but the behavioral context is strong.

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?

Information-dense and front-loaded with the return/ordering rule, then routing, then edge cases. Every clause carries weight, though the pace sentence is long and slightly buries the practical takeaway.

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?

There is no output schema, so the description must carry return semantics, and it does: total, not_scored, and pace are all explained. For a filtered, side-effecting digest tool with annotations covering the safety profile, this is nearly complete; only explicit auth/permission context is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all four parameters, including defaults, the display.today rule for limit, and the per-job scoring cost for score_top. The description only gestures at the limit ('matched before the limit') and adds no parameter syntax beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb+resource (a digest of new jobs that pass the watchlist's filters) and its ordering rule (fit score, then keyword relevance). It explicitly distinguishes itself from list_queued_jobs and list_applications, so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('finding jobs to consider'), a prerequisite ('call fetch_jobs first to pick up today's postings'), and named alternatives for adjacent intents (list_queued_jobs, list_applications). It also encodes the pace rule, including the 'never refuse to help' guardrail.

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