Skip to main content
Glama

Check jobs are open

check_jobs_open
Read-onlyIdempotent

Whether each of up to 50 jobs, by the ids a search gave, is still open: open (seen on the employer's site in the last 3 days), unconfirmed (not seen for longer, so it may have closed), closed, or unknown, with when it was last seen.

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": {
      "ids": "<ids>"
    },
    "name": "check_jobs_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the four-way status vocabulary, the concrete 3-day freshness threshold that separates 'open' from 'unconfirmed', and the caveat that unconfirmed 'may have closed'. It does not discuss rate limits or how unknown arises, which keeps it below a 5.

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 the resource and scope first, followed by tightly packed status definitions that each carry distinct information. Nothing is redundant and no sentence is filler.

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?

The tool is simple (one array parameter) and has no output schema, so the description carries the burden of explaining return values — and it does, defining all four statuses plus the last-seen timestamp. Combined with the annotations, an agent has everything needed to call and interpret it correctly.

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?

Only one parameter exists, and the description adds meaning beyond the schema by explaining where the ids come from (a prior search) and that the batch is capped at 50. Those are operational constraints an agent needs to plan calls, not just a restatement of the field. The id format itself is left to the schema.

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 states a specific verb and resource: checking whether each of up to 50 jobs, by id, is still open, and it enumerates the four possible statuses. It is clearly distinguishable from search_jobs and get_job by its batch-id scope, though it never names a sibling explicitly. The implicit link 'by the ids a search gave' helps an agent see the workflow without spelling out the alternative tool.

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

Usage Guidelines4/5

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

It gives clear usage context: pass ids that a search produced, up to 50 at a time, which tells the agent this is a post-search enrichment step rather than a discovery tool. It stops short of stating when NOT to use it or naming alternatives such as get_job for single-record detail. That is a real but modest gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources