Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (96 Tools)

greenhouse_ai_ml_engineering_jobs_radar

Read-onlyIdempotent

Greenhouse AI & ML Engineering Jobs Radar: Real-time feed of AI, ML, and LLM engineering job openings from leading AI companies.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum AI/ML job listings to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum AI/ML job listings to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that results are a 'real-time feed' and that the source is Greenhouse data about leading AI companies, which is useful freshness/source context. It does not disclose ordering, result shape, or whether listings are deduplicated.

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?

A single sentence, front-loaded with the resource and domain, with no filler. It is slightly redundant with the tool name and annotations title but wastes no space.

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 zero-required-parameter read tool with full annotation coverage and full schema coverage, this is roughly sufficient. With no output schema, however, the description never indicates what fields a listing contains (title, company, location, posting date), which an agent would want before calling.

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?

Only one optional parameter, and the schema documents it fully at 100% coverage ('Maximum AI/ML job listings to return'), so the baseline applies. The description adds nothing about default behavior or pagination beyond what the schema says.

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 resource and scope: a real-time feed of AI/ML/LLM engineering job openings sourced from Greenhouse at leading AI companies. An agent can tell this apart from the cybersecurity, fintech, and general German job siblings by the AI/ML engineering focus, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternative tools for adjacent job data (e.g. the cybersecurity or general jobs boards). The agent must infer applicability purely from the description's topic wording.

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