Skip to main content
Glama

OfferMagnet Jobs

Job market stats

job_market_stats
Read-onlyIdempotent

Counts of live postings by country, contract type, remote and visa wording, from the same index.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered structurally. The description adds two genuinely useful behavioral facts beyond that: only 'live' postings are counted, and the data comes 'from the same index' as the search tools. It says nothing about freshness, caching, or the shape of the returned counts.

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?

A single dense sentence that front-loads the verb and enumerates the breakdown dimensions with no filler. The trailing 'from the same index' is slightly opaque phrasing but earns its place by tying the numbers to the search corpus.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only aggregate tool the description covers what is counted and along which axes, which is close to sufficient. It leaves unclear whether the counts are always unfiltered/global and what the response structure looks like, though the absence of an output schema makes the latter a smaller concern.

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?

The tool takes zero parameters and the schema coverage is 100%, so there is no parameter semantics burden to discharge. Baseline 4 applies for a no-argument tool.

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?

States a specific verb and resource ('counts of live postings') plus the exact breakdown dimensions (country, contract type, remote, visa wording), which clearly separates it from the per-posting siblings get_job and search_jobs. It never names those siblings explicitly, so differentiation is inferred rather than stated.

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?

The word 'counts' implies this is the aggregate companion to search_jobs, so an agent can reasonably infer when to reach for it. However, there is no explicit when-to-use or when-not-to-use statement, and no mention of whether results can be scoped to a query or are always global.

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