Skip to main content
Glama

Enterprise B2B Lead, Tech Stack & Regulatory Signal MCP

Extract Live ATS Hiring Signals

extract_ats_hiring_signals
Read-onlyIdempotent

Fetches live open job count and active roles for a company slug across Greenhouse, Ashby, and Lever.

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": {
      "company_slug": "<company_slug>"
    },
    "name": "extract_ats_hiring_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
company_slugYesATS board slug such as vercel, stripe, or linear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new behavioral context: the data is live (not cached), and it is aggregated across three named ATS providers. It says nothing about behavior when a slug does not exist on one or more providers, rate limits, or latency, which is the remaining gap.

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 front-loaded sentence with the resource and source list in the first clause and zero filler. Nothing could be removed without losing information.

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?

For a one-parameter read-only tool with no output schema, the description covers what is fetched and from where. It could be slightly more complete by stating how results are aggregated or what happens when a provider has no board for the slug, but nothing essential 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 description coverage is 100% and the schema already gives example slugs (vercel, stripe, linear), so the baseline is 3. The description adds a small amount of meaning by implying one company slug is queried across all three providers, but it offers no format or fallback detail beyond the schema.

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?

The description gives a specific verb ('Fetches'), a specific resource ('live open job count and active roles'), and names the three sources (Greenhouse, Ashby, Lever), which is enough for an agent to distinguish this from the unrelated siblings. It stops short of explicitly contrasting itself with any named alternative, so it lands at 4 rather than 5.

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 prerequisites or alternatives are mentioned. The agent must infer from the single sentence when live ATS hiring data is the right call versus the sibling tools.

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.