Skip to main content
Glama

Worklittle Jobs

Jobs · Get Market Overview

get_market_overview
Read-onlyIdempotent

Jobs — Returns aggregate job-market statistics from Worklittle. Call with no args for the whole market (workplace and job-type mix, top hiring companies). When the user names a role and/or city (e.g. product managers in San Francisco), pass query and location. The filtered slice includes match count, top companies in the sample, and salary signals from listings that publish pay.

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

Input Schema

NameRequiredDescriptionDefault
queryNoRole or title filter for a market slice (e.g. product manager).
locationNoLocation substring for a market slice (e.g. San Francisco).
workplace_typeNoOptional workplace filter for the slice.

Output Schema

NameRequiredDescriptionDefault
top_hiring_companiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / properties / top_companies
      Removed value: -{
      -  "items": {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / top_hiring_companies
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedOutput schema / properties / total_jobs
      Removed value: -{
      -  "type": "number"
      -}
  2. Changed3 schema fields changed
    • addedInput schema / properties / location
      Added value: +{
      +  "description": "Location substring for a market slice (e.g. San Francisco).",
      +  "type": "string"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Role or title filter for a market slice (e.g. product manager).",
      +  "type": "string"
      +}
    • addedInput schema / properties / workplace_type
      Added value: +{
      +  "description": "Optional workplace filter for the slice.",
      +  "enum": [
      +    "remote",
      +    "hybrid",
      +    "on_site"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the description correctly spends its space on output shape per mode: workplace/job-type mix and top companies unfiltered, versus match count, sampled top companies, and salary signals when filtered. That modal difference is real value the annotations cannot express.

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?

Three sentences, front-loaded with the core purpose, then the no-arg behavior, then the filtered behavior — a logical progression with no filler. The leading 'Jobs —' prefix is redundant with the title but harmless.

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?

With an output schema present, the description need not detail return values, and it still summarizes what each mode yields. Annotations carry the safety profile. The only remaining gap is describing merged filtering behavior (query plus location together) and workplace_type, which is minor.

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 coverage is 100%, so the schema already documents all three parameters and the enum values. The description adds the semantic that the parameters form a filterable 'slice' and that omitting them yields the whole market, but it never mentions workplace_type, so it adds only modest meaning beyond 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 gives a specific verb and resource ('Returns aggregate job-market statistics') and names the source (Worklittle), which clearly separates it from listing-level siblings like search_jobs or get_job_details. It is clear without needing the schema, though it never explicitly contrasts itself with a sibling.

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 states both usage modes concretely: call with no args for the whole market, or pass query and/or location when the user names a role or city, complete with an example. It stops short of naming an alternative tool for when an agent should prefer per-listing search instead.

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