Skip to main content
Glama
Jobs Every Hour MCP server

Jobs Every Hour MCP server

Jobs by skill

jobs_by_skill

Find open jobs that require a specific skill, like Python, React, SQL, Kubernetes, or Salesforce. Narrow results to remote roles and set how many postings to return.

Instructions

Open jobs that ask for a skill, such as Python, React, SQL, Kubernetes or Salesforce.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "skill": "<skill>"
    },
    "name": "jobs_by_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the newest jobs to show, 1 to 30
skillYesA skill, e.g. Python
remote_onlyNoOnly remote jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does add one useful trait beyond the schema: results are limited to 'open' jobs, which is not expressible via any parameter. However, it says nothing about ordering, empty-result behavior for an unrecognized skill, or result completeness, leaving meaningful behavioral gaps for a no-annotation tool.

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?

A single short sentence with the resource and filter front-loaded and zero filler. Nothing in it is redundant or padded, and it is readable in one pass.

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 simple three-parameter read tool with full schema coverage and no output schema, the description covers the essentials of what it returns. It still omits ordering and result-count expectations at the description level (ordering appears only via the limit param) and gives no signal about how skill matching behaves, which is the main thing an agent could get wrong.

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 description coverage is 100%, so the schema already documents all three parameters, including the 1-30 limit and the 'newest jobs' ordering. The description's skill examples (React, Kubernetes, Salesforce) loosely extend the schema's single 'e.g. Python' hint, but add no detail about matching semantics such as case sensitivity, partial matches, or alias handling.

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+resource combination: it returns open jobs filtered by a skill, with concrete skill examples (Python, React, SQL, Kubernetes, Salesforce). This is clearly distinguishable from jobs_by_category, jobs_by_company, and jobs_by_location by the name and the 'ask for a skill' phrasing, though it never explicitly names those alternatives.

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?

Usage is only implied: an agent can infer it should call this when the query is skill-based rather than company-, location-, or category-based. There is no explicit 'use this instead of X when...' routing, no mention of prerequisites, and no statement of when this tool is a poor fit (e.g., broad browsing, which latest_jobs likely covers).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.