Skip to main content
Glama

getwork.dev

Market overview

market_overview
Read-onlyIdempotent

The whole index at a glance: active jobs, companies, how many publish a salary, and the most requested technologies. Takes no input; use search_jobs or salary_insights to narrow down.

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_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
companiesNo
top_stackYes
active_jobsYes
jobs_with_salaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuine context beyond that: it takes no input and returns aggregate counts plus a 'most requested technologies' ranking, which tells the agent this is a cheap constant snapshot.

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 sentences, front-loaded with what comes back and closed with where to go instead. Every clause carries information; nothing is repeated from the name, annotations, or schema.

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 and rich annotations, the description needs only to define scope and routing, and it does both. The one unaddressed point is freshness — whether these counts are live or a periodic snapshot — which matters for an index-wide aggregate.

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?

With zero parameters the baseline is 4, and the description explicitly confirms 'takes no input,' removing any ambiguity. It adds the useful consequence that no scoping arguments exist, so filters must come from a different tool.

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?

The description names the exact aggregate this tool returns — active jobs, companies, salary-publication counts, top technologies — rather than restating the name. It also scopes it as 'the whole index at a glance,' which makes it immediately distinguishable from the narrower siblings.

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 gives an explicit routing rule: use this for the broad view, and use search_jobs or salary_insights to narrow down. It doesn't spell out a when-not-to-use case (e.g., don't call it for a specific company's stats), so it falls just short of a full 5.

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