Skip to main content
Glama

Hyreflow

by ai.hyreflow
OverviewDiscussionsAdmin

hyreflow_shortlist

Destructive

Bulk-screen candidates against a job description: one structured decision per candidate, ranked by score, with a tier (tier_1 | tier_2 | no_fit | unscored) and per-category scores. Takes job_spec plus either candidates (up to 1000 row objects, e.g. what a CRM/ATS search returned) or input (a ds_ dataset id, for a larger pool). Rows need work history; a pool of sourcing stubs without it is refused. The question set is generated from the job spec once and reused for every later screen of it. The call waits about 20s: a finished screen returns the top 25 ranked rows (name, row, shortlist cell); an unfinished one (including every first screen of a new job spec, which also writes its questions) returns {run_id, status, progress, poll_after_s}, and a call with only run_id returns the ranking once ready, at no charge. Every row, full profile included, is stored in the dataset at _meta.dataset_id. Resending an identical screen within 15 minutes returns the first one, charged 0. dry_run: true quotes the cost without running. Charges credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoA ds_ dataset id to screen instead of `candidates`.
run_idNoThe `run_id` of an earlier screen that returned unfinished. Sent alone, it returns that screen's progress or ranking. Free.
dry_runNo
job_specNoThe job description text.
min_scoreNo
questionsNoA custom question set to use instead of the generated one.
candidatesNo
must_havesNoHard requirements, each a pass/fail gate.
user_promptYesThe user's request that drove this call, verbatim as they phrased it. Recorded with the run so its trace reads as the ask followed by the calls it drove.
confirm_tokenNoThe `confirm_token` returned by a previous identical call that came back `confirmation_required`. Required to run a call above the workspace's confirmation threshold.
allow_thin_profilesNo
regenerate_questionsNoReplace this job spec's stored question set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / confirm_token / description
      Previous value: -"Echo of the `confirm_token` a previous identical call returned with `confirmation_required`, after the user approved the quoted cost."New value: +"The `confirm_token` returned by a previous identical call that came back `confirmation_required`. Required to run a call above the workspace's confirmation threshold."
    • changedInput schema / properties / must_haves / description
      Previous value: -"Hard requirements, each a pass/fail gate. Confirm them with the user first."New value: +"Hard requirements, each a pass/fail gate."
    • changedInput schema / properties / questions / description
      Previous value: -"Your own question set instead of the generated one — shapes in shortlist.md."New value: +"A custom question set to use instead of the generated one."
    • changedInput schema / properties / run_id / description
      Previous value: -"Poll a screen an earlier call handed back unfinished — send only this (and user_prompt). Free."New value: +"The `run_id` of an earlier screen that returned unfinished. Sent alone, it returns that screen's progress or ranking. Free."
    • changedInput schema / properties / user_prompt / description
      Previous value: -"The user's request that drove this call, verbatim as they phrased it. Never a paraphrase, and never ask the user for it."New value: +"The user's request that drove this call, verbatim as they phrased it. Recorded with the run so its trace reads as the ask followed by the calls it drove."
  2. Changed2 schema fields changed
    • addedInput schema / properties / run_id
      Added value: +{
+  "description": "Poll a screen an earlier call handed back unfinished — send only this (and user_prompt). Free.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "job_spec",
-  "user_prompt"
-]New value: +[
+  "user_prompt"
+]
  3. Changed2 schema fields changed
    • removedInput schema / properties / async
      Removed value: -{
-  "type": "boolean"
-}
    • addedInput schema / properties / regenerate_questions
      Added value: +{
+  "description": "Replace this job spec's stored question set.",
+  "type": "boolean"
+}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: it charges credits, `dry_run` quotes without running, identical resends within 15 minutes are deduped and charged 0, calls block ~20s then either return top 25 or a run_id polling handle, run_id-only calls are free, and every row is persisted at `_meta.dataset_id`. This is far more context than destructive/openWorld hints alone convey.

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?

Dense but front-loaded: the core purpose and output shape come first, then input modes, then async/cost/idempotency behavior. Nearly every sentence carries distinct operational information, though the single-paragraph density is heavier than ideal.

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

Completeness5/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 carries the full burden of explaining returns and does so (top 25 ranked rows with name/row/shortlist cell, versus run_id/status/progress/poll_after_s), plus the async and billing model. For a 12-parameter, nested, side-effecting tool this is unusually complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 67% schema coverage, the description meaningfully enriches the key parameters: `candidates` (up to 1000 row objects, e.g. CRM/ATS output), `input` (ds_ dataset id for larger pools), `run_id` (sent alone returns ranking free), and `dry_run` (cost quote). It leaves `min_score`, `must_haves`, `allow_thin_profiles`, and the confirm_token flow largely to the schema.

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 ('bulk-screen candidates against a job description') and immediately pins down the output shape (one structured decision per candidate, ranked by score, with a tier and per-category scores). This is far more specific than the sibling tools (enrich_job, skill_search, dataset_read) and lets an agent distinguish it without opening the 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 explicit scenario guidance: pass `candidates` for CRM/ATS rows vs `input` for a larger ds_ dataset pool, send `run_id` alone to poll free, and note that a first screen of a new job spec always returns unfinished. It also states a when-not condition (thin sourcing stubs are refused). It does not name sibling alternatives, so it falls short of a full 5.

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

All Hyreflow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources