Skip to main content
Glama

Hyreflow

hyreflow_enrich_job

Read-only

Fetch an async enrichment job by its job id (the job handle on a still_enriching row). Returns status (pending | settled | failed | expired), credits charged, the email when settled, and the result. A still_enriching row is NOT a miss: its job usually settles within 1-2 minutes, so a pending status means check again later. A job that settles with no email skipped the chain's later providers for that row. Free.

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": {
      "job_id": "<job_id>"
    },
    "name": "hyreflow_enrich_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "provider",
      -  "job_id"
      -]New value: +[
      +  "job_id"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it enumerates the four possible statuses, states credits charged and that the call is free, gives the expected settle time, and explains that a settled job with no email means later providers in the chain were skipped. That is exactly the behavioral context an agent needs to interpret an empty result correctly.

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?

Front-loaded with the action and return fields, then the interpretation rules. Dense but nearly every clause earns its place; the parenthetical status list and the repeated 'check again later' phrasing add slight redundancy.

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?

With no output schema, the description properly spells out return values (status, credits, email, result) and how to interpret each status. The one real gap is the undocumented `provider` parameter, which leaves the caller guessing on optional input.

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 0%, so the description must carry the load. It does clarify `job_id` usefully (a handle from a `still_enriching` row), but the `provider` parameter is never mentioned and remains completely undefined.

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: fetch an async enrichment job by its job id, plus where that id comes from (the `job` handle on a `still_enriching` row). That origin clause implicitly separates it from the run/start tool, so an agent can tell which one to call without opening a 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 when-to-use guidance: a `still_enriching` row is not a miss, and a `pending` status means check again later within 1-2 minutes. It never names the sibling that starts a job, so the exclusions are implied rather than explicit.

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.