Skip to main content
Glama
Sign In
jobscan-mcp

jobscan-mcp

by aminafara123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

market_stats

Read-onlyIdempotent

Track daily counts of relevant and new job postings over a set number of days to gauge niche market activity from reports.

Instructions

Per-day counts of relevant and new postings over the last N days, parsed from the reports: a quick pulse of the niche market.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds useful context that the counts are derived from existing reports and that they cover both relevant and new postings. It says nothing about rate limits, cost, or data freshness/lag beyond the report-parsing note.

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?

One sentence that front-loads the output shape and then characterizes the tool's role. It is efficiently sized with no filler, though "a quick pulse of the niche market" is slightly promotional rather than informative.

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 single-optional-param, read-only aggregation tool, this is close to sufficient; the output schema exists so return values need not be re-explained. What's missing is any indication of how the result is scoped (e.g. which market/niche is being measured), which matters given the description's ambiguity about scope.

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?

Schema coverage is 0%, but the single "days" parameter is semantically explained by "over the last N days", which tells the agent the window is a trailing range rather than a calendar range. The 30-day default is only visible in the schema, which is acceptable.

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 specific output (per-day counts of relevant and new postings) and the source (parsed from the reports), so an agent knows exactly what this tool produces. It doesn't reference any sibling (latest_report, search_jobs, is_seen), so differentiation from nearby tools is left to inference.

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?

"A quick pulse of the niche market" implies a summary/overview use case, which gives some sense of when to reach for it. However, there is no explicit when-to-use vs. when-not, and no routing to alternatives like latest_report or search_jobs for detailed data.

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