Skip to main content
Glama

Nectar Jobs

Count jobs in a slice of the market

aggregate_jobs
Read-onlyIdempotent

Aggregate counts for a filtered slice of the corpus — the tool for market/trend questions ("what kinds of roles are hiring in Pune?"), instead of issuing many limit-1 searches.

Takes the same filters as search_jobs (keyword matching included, see its ``query`` note) and
returns the slice's ``total`` plus breakdowns, each a {value: count} dict, biggest first:
``by_category`` (job function — the role-type axis), ``by_seniority``,
``by_employment_type`` (contract basis and hours in one axis; ``full_time`` is inflated because
a posting silent about its hours is recorded as full-time), ``top_companies``,
``top_skills``, ``by_source``, ``benefits``, ``company_size``, ``lang``, and ``salary`` —
per-currency posting counts with salary_max quartiles (currencies deliberately not blended).
Every count collapses duplicate postings, so numbers are comparable to search totals. A
breakdown on a field you filtered by lists only the values you filtered to.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
remoteNo
sourceNo
companyNo
countryNo
categoryNo
locationNo
seniorityNo
salary_minNo
employment_typeNo
posted_since_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds non-obvious semantics: duplicate postings are collapsed so counts match search totals, a breakdown on a filtered field returns only the filtered values, and full_time is inflated because hour-silent postings default to it. It also flags that currencies are deliberately not blended in the salary axis — exactly the kind of caveat an agent cannot infer from structured fields.

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?

Front-loaded with purpose and the alternative it replaces, then a compact enumeration of breakdown axes. The parenthetical caveats are dense but each carries real information; the one cost is that the middle sentence packs ten breakdown names plus qualifiers into a single sprawling clause.

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 an 11-parameter aggregate tool with an output schema, the description is largely sufficient: it explains the shape of each breakdown ({value: count}, biggest first) and interprets the tricky axes. The remaining hole is per-filter semantics, which are outsourced to search_jobs rather than stated here.

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

Parameters2/5

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

With 11 parameters at 0% schema description coverage, the description must carry parameter meaning, but it only says the filters mirror search_jobs and defers keyword behavior to that tool's 'query' note. Individual parameters (remote, salary_min, posted_since_days, employment_type values) get no interpretation, so an agent must open the sibling tool to understand the main inputs.

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 and resource — 'aggregate counts for a filtered slice of the corpus' — and immediately distinguishes itself from issuing 'many limit-1 searches'. It explicitly names the market/trend question shape it serves, so an agent can tell it apart from search_jobs without reading either schema.

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?

Gives clear when-to-use guidance ('market/trend questions') and an explicit anti-pattern to avoid (many limit-1 searches), and points to search_jobs as the filter-equivalent tool. It stops short of saying when a single search_jobs call is still preferable, or how it differs from get_stats / job_trends.

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