Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

greenhouse_cybersecurity_soc_hiring_monitor

Read-onlyIdempotent

Greenhouse Cybersecurity & Cloud SecOps Hiring Radar: Real-time structured data extraction feed for Greenhouse Cybersecurity & Cloud SecOps Hiring Radar.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records 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 number of records 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

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered structurally. The description adds only the vague qualifier 'Real-time,' without saying whether data is scraped live, cached, refreshed on a schedule, or what the freshness window is — and openWorldHint implies external variability the description never addresses.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the second clause after the colon repeats the first clause almost word for word, so the sentence earns nothing. Brevity here reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

The tool is simple (one optional param, no output schema), but the description still leaves the agent unable to predict what a 'record' contains — a job posting, a company, a role count, a trend datapoint? With no output schema, the description carries the burden of describing the return payload and does not.

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% with a single optional parameter (maxResults) that documents itself as the maximum number of records returned. The description contributes nothing extra about bounding, pagination, or default behavior, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a near-verbatim restatement of the tool name and title: 'Hiring Radar' is described as a 'feed for ... Hiring Radar.' The phrase 'structured data extraction feed' hints at retrieval, but no verb+resource statement (e.g. 'fetch open job postings') tells an agent what records are actually returned or in what shape.

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 guidance at all, and no differentiation from the many closely related siblings such as greenhouse_b2b_tech_hiring_velocity_scraper or greenhouse_fintech_compliance_hiring_tracker. An agent must guess from the domain words 'Cybersecurity & Cloud SecOps' alone whether this tool applies to a given request.

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