Skip to main content
Glama

check_job

Verify if a job listing link is still open and return its status, reason, and full description when active.

Instructions

Check whether a job link is still open. Returns status open, closed or unknown, the reason, and the full job description when it is open.

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": {
      "url": "<url>"
    },
    "name": "check_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return contract well (three status values, a reason field, and the full description only when open). It says nothing about whether this performs a live fetch, expected latency, caching, auth requirements, or how errors/rate limits surface — relevant for a tool that presumably hits an external site.

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 tight sentences: the first states the operation, the second front-loads the return values. No filler, and the most decision-relevant information (the status vocabulary) arrives immediately.

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?

This is a low-complexity one-parameter tool with no output schema, and the description covers both the action and the shape of the result. The remaining gap is the meaning of 'unknown' — whether it signals an error, a blocked fetch, or a transient failure — which an agent would need in order to react.

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 description coverage is 0% for the single 'url' parameter, so the description must compensate. It does clarify that the url is a 'job link', which is more than the bare schema says, but it gives no format guidance (canonical URL vs. redirect, absolute vs. relative).

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 concrete verb and object: check whether a given job link is still open, and it enumerates the returned statuses (open/closed/unknown) plus the conditional full description. That clearly separates it from search/list siblings like search_jobs or company_jobs, though no sibling is named explicitly.

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 only implied: an agent infers it should call this when it already has a job URL and needs liveness. There is no explicit statement of when not to use it, no mention of what to do with an 'unknown' result, and no pointer to an alternative for discovery-style lookups.

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