Skip to main content
Glama
Sign In

Good Turn Studio (all tools)

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

Job Spotter: The companies hiring most right now, with trends and pay

jobspotter_top_hiring_companies
Read-onlyIdempotent

Job Spotter. The companies hiring most right now, with trends and pay. For "who's hiring the most data people in the UK?", "which companies are growing?", "who's hiring remotely?". Ranks employers in Job Spotter's index by open roles, each with roles added and taken down this week, its trend (growing, steady or contracting), the change on the week before, median advertised pay, AI roles, its careers page and any US layoff notices in the last 90 days. Then call search_jobs with the company name for its roles. A ready-to-read summary is in say.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many companies, 1 to 30 (default 15).
trendNoOptional: growing, steady or contracting.
whereNoOptional town or city (for example London or Austin), or remote.
countryNoOptional country by name or two-letter code, for example United Kingdom, US or DE. Leave out for worldwide.
functionNoOptional job area: software, data (data and AI), design, product, sales, finance, marketing, customer, healthcare, education, people, legal, operations, hardware, service or management. A job word such as "nurse" works too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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, so the safety bar is low. The description still earns credit by enumerating exactly what each ranked row contains, including recency windows ("this week", "change on the week before", "US layoff notices in the last 90 days"), which is real behavioral context the annotations do not supply.

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?

Purpose is front-loaded and the rest of the text is dense with distinct, useful facts rather than filler. There is mild redundancy in the opening two clauses ("Job Spotter. The companies hiring most right now, with trends and pay" repeats the title) and the long field enumeration is a single run-on sentence.

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

Completeness5/5

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

No output schema exists, so the description deliberately covers the return shape field by field, notes the ready-to-read `say` summary, and points to the next tool for drill-down. Despite five optional filters, nothing an agent needs to call it correctly is missing.

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% and every parameter already carries an inline description and enum, so the schema does the heavy lifting. The example questions imply how to combine filters (function + country, where + function), but the description never names the parameters or their accepted values, so it adds only marginal meaning beyond the schema.

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: it ranks employers in Job Spotter's index by open roles, with named attributes (weekly adds/removals, trend, prior-week change, median pay, AI roles, careers page, US layoffs). It also routes the agent onward to search_jobs for the individual roles, so it is separable from sibling tools without opening the 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 concrete triggering questions ("who's hiring the most data people in the UK?", "which companies are growing?", "who's hiring remotely?") that map onto the filter parameters, plus an explicit follow-up path ("Then call search_jobs with the company name for its roles"). It does not state when NOT to use it, e.g. against company_lookup for a single employer, so it stops 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.

All Good Turn Studio (all tools) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources