StackFast FractWin Expert Brain

Talent Scout Set Search Rails

talent_scout_set_search_rails

Read-only

Persist the active Talent Scout search strategy for a tenant: target lanes, compensation floor, geography, positive/negative filters, resume-variant priority, travel posture, and voice anchor. Future search, fit, review, compose, packet, and note calls load these rails by default until superseded.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`active`	No
`reason`	No
`priority`	No		primary
`geography`	No
`rail_name`	Yes
`tenant_id`	No
`sqlite_path`	No	Optional local SQLite path for BYOC receipts; hosted cloud calls fail closed instead of reading local files.
`age_strategy`	No
`target_lanes`	No
`voice_anchor`	No
`auth_token_key`	No	Optional wallet/env key name for the tenant Turso auth token. Never pass a raw token.
`database_url_key`	No	Optional wallet/env key name for the tenant Turso database URL. Never pass a raw URL or secret.
`negative_filters`	No
`owner_profile_id`	No
`positive_filters`	No
`compensation_floor`	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.
`resume_variant_priority`	No

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.

Changed2 schema fields changedJul 9, 2026
- removedInput schema / properties / applicant_profile_id
```
Removed value: -{
-  "type": "string"
-}
```
- addedInput schema / properties / owner_profile_id
```
Added value: +{
+  "type": "string"
+}
```

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 19, 2026

TDQS

B3.2/5.0

Behavior1/5

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

Annotation Contradiction: the description says 'Persist' the active search strategy and that future calls 'load these rails by default until superseded', which strongly implies a state-changing write operation. Yet annotations declare readOnlyHint=true, signaling the tool does not modify state. This is a direct and serious inconsistency that would misled an agent.

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?

Two sentences and appropriately front-loaded: the verb and resource come first, followed by the field list and downstream effect. The first sentence is a bit long but still readable. No wasted filler; the 'until superseded' detail earns its place.

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 a complex 18-parameter, nested-object tool with only 22% schema description coverage, the description does not fully equip an agent. It communicates the core persistence behavior and default-loading nicely, but it leaves required rail_name and most parameters unexplained, and the readOnlyHint contradiction undermines trust in the tool's actual behavior.

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 22%, so the tool description must compensate for the 18 parameters. It lists several search-strategy parameters by name, but adds little meaning beyond the property names, and it omits the required rail_name semantics, active, priority, reason, tenant_id, owner_profile_id, and the nested objects. It also mentions 'travel posture', which does not appear anywhere in 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?

The description names a specific verb ('Persist') and resource ('active Talent Scout search strategy') and enumerates the strategy fields: target lanes, compensation floor, geography, filters, resume-variant priority, travel posture, voice anchor. It clearly distinguishes this from the many talent_scout_* sibling calls by framing it as the persistent defaults-setter for future search/fit/review/compose/packet/note operations.

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?

The description gives clear context about when this matters: future search, fit, review, compose, packet, and note calls load these rails by default until superseded. This implies use it to establish or update the tenant's persistent search defaults, though it does not explicitly state when not to use it or name alternatives.

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?