StackFast FractWin Expert Brain

Talent Scout Scan Company For Roles

talent_scout_scan_company_for_roles

Read-onlyIdempotent

Preview a qualified company target for direct careers URLs and role-lane matches. Returns verified status receipts such as company_careers_open_role, needs_human_url_verification, needs_jd_hydration, or careers_page_no_relevant_role. Read-only by default: it returns exact role records for human review, does not persist queue rows unless persist_results is explicitly true, and never invents jobs.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`tenant_id`	No
`source_url`	No
`campaign_id`	No
`careers_url`	No
`sqlite_path`	No	Optional local SQLite path for BYOC receipts; hosted cloud calls fail closed instead of reading local files.
`company_name`	No
`target_lanes`	No
`auth_token_key`	No	Optional wallet/env key name for the tenant Turso auth token. Never pass a raw token.
`company_domain`	No	Backward-compatible alias for company_homepage_url; bare domains are normalized to https://<domain>.
`persist_results`	No	When true, persist verified role records and role-scan receipts to Talent Scout. Defaults false so hosted MCP scans remain read-only previews for human review.
`database_url_key`	No	Optional wallet/env key name for the tenant Turso database URL. Never pass a raw URL or secret.
`company_target_id`	No
`target_role_lanes`	No
`eligible_countries`	No
`allow_live_firecrawl`	No	Backward-compatible no-op for this scanner; official ATS/API scans are preferred when available.
`company_homepage_url`	No
`tenant_database_type`	No	Optional physical database routing mode. Omit for the default internal StackFast DB; use sovereign_cloud only with wallet-resolved tenant DB credentials.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No
`public_tool`	Yes
`drafts_never_sends`	No
`no_autonomous_outbound`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 8, 2026

changedInput schema / properties / persist_results / description

Previous value: -"When true, persist verified role leads and role-scan receipts to Talent Scout. Defaults false so hosted MCP scans remain read-only previews for human review."New value: +"When true, persist verified role records and role-scan receipts to Talent Scout. Defaults false so hosted MCP scans remain read-only previews for human review."

Changed1 schema field changedJul 1, 2026

addedInput schema / properties / persist_results

Added value: +{
+  "default": false,
+  "description": "When true, persist verified role leads and role-scan receipts to Talent Scout. Defaults false so hosted MCP scans remain read-only previews for human review.",
+  "type": "boolean"
+}

Changed2 schema fields changedJul 1, 2026

addedInput schema / properties / allow_live_firecrawl

Added value: +{
+  "default": false,
+  "description": "Backward-compatible no-op for this scanner; official ATS/API scans are preferred when available.",
+  "type": "boolean"
+}

addedInput schema / properties / company_domain

Added value: +{
+  "description": "Backward-compatible alias for company_homepage_url; bare domains are normalized to https://<domain>.",
+  "type": "string"
+}

Changed6 schema fields changedJun 25, 2026

addedInput schema / properties / careers_url
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / eligible_countries

Added value: +{
+  "default": [
+    "US"
+  ],
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 10,
+  "maximum": 25,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / source_url
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / target_lanes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / target_role_lanes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed4 schema fields changedJun 25, 2026

addedInput schema / properties / auth_token_key

Added value: +{
+  "description": "Optional wallet/env key name for the tenant Turso auth token. Never pass a raw token.",
+  "type": "string"
+}

addedInput schema / properties / database_url_key

Added value: +{
+  "description": "Optional wallet/env key name for the tenant Turso database URL. Never pass a raw URL or secret.",
+  "type": "string"
+}

addedInput schema / properties / sqlite_path

Added value: +{
+  "description": "Optional local SQLite path for BYOC receipts; hosted cloud calls fail closed instead of reading local files.",
+  "type": "string"
+}

addedInput schema / properties / tenant_database_type

Added value: +{
+  "description": "Optional physical database routing mode. Omit for the default internal StackFast DB; use sovereign_cloud only with wallet-resolved tenant DB credentials.",
+  "enum": [
+    "internal",
+    "sovereign_cloud",
+    "byoc"
+  ],
+  "type": "string"
+}

AddedJun 22, 2026

TDQS

A3.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that queue rows are not persisted unless persist_results is explicitly true, that receipts are verified, and that the tool never invents jobs. This clearly sets expectations and aligns with the readOnly and idempotent hints.

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?

The description is three focused sentences: purpose, receipt vocabulary, and persistence/safety contract. There is no filler, and the most important behavioral caveat is front-loaded.

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?

For an 18-parameter tool with zero required parameters, the description never explains how to identify the target company or which inputs are expected. The output schema may cover return values, but input selection and sibling-tool routing are significant gaps.

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

Parameters2/5

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

Schema description coverage is only 39%, and the description does not clarify key inputs like company_target_id, company_name, company_homepage_url, careers_url, target_lanes versus target_role_lanes, or eligible_countries. It only indirectly explains persist_results, leaving most of the 18-parameter surface under-documented.

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 clearly states the tool previews a qualified company target, finds direct careers URLs and role-lane matches, and returns specific status receipts. It is specific about verb, resource, and output, but does not explicitly contrast itself with sibling talent_scout discovery/search tools.

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

Usage Guidelines3/5

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

The read-only and human-review wording implies this is a safe pre-scan tool, but there is no explicit when-to-use/when-not-to-use guidance and no named alternatives. Given the large sibling set, more explicit routing would be valuable.

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

All StackFast FractWin Expert Brain tools Inspect

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

Need Help?