StackFast FractWin Expert Brain

Talent Scout Daily Pipeline

talent_scout_daily_pipeline

Read-only

Return the closed-loop Talent Scout daily operating report from the shared tenant queue: applied pipeline, mailbox reconciliation status, follow-up due, open roles, availability checks, preference filters, stale/closed rows, new discoveries, bounded needs_role_hydration recovery, and a 3-5 role slate. Mailbox reconciliation runs server-side via the StackFast service-account reader. Clients MUST NOT invoke their own Gmail/email connector; if mailbox_reconciliation_status is not ok, surface the red receipt and stop instead of substituting a client-side mailbox read. Read-only control-tower view; no sends or applications.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`compact`	No	Return counts, status buckets, mailbox status, and a bounded slate without full bucket payloads. Defaults true for hosted MCP latency.
`profile`	No	Alias for owner_profile when reviewing stale queue items.
`tenant_id`	No
`slate_limit`	No
`include_items`	No	Return top-level queue cards. Defaults false so compact daily reads return the bounded operating summary only.
`owner_profile`	No	Optional owner preference context used to refresh stale zero-score queue items inside this tenant only.
`section_limit`	No
`hydration_limit`	No	Bounded live-hydration attempts for thin roles before compose. Reports attempts and remaining needs_role_hydration; never applies or sends.
`include_applied`	No	Include already-applied rows in the applied/waiting pipeline buckets.
`include_archived`	No	Include archived, rejected, passed, stale, or already-applied rows. Defaults false for active work queues.

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

addedInput schema / properties / include_items

Added value: +{
+  "default": false,
+  "description": "Return top-level queue cards. Defaults false so compact daily reads return the bounded operating summary only.",
+  "type": "boolean"
+}

Changed3 schema fields changedJul 9, 2026

removedInput schema / properties / candidate_profile

Removed value: -{
-  "description": "Optional profile used to refresh stale zero-score queue items inside this tenant only.",
-  "type": "object"
-}

addedInput schema / properties / owner_profile

Added value: +{
+  "description": "Optional owner preference context used to refresh stale zero-score queue items inside this tenant only.",
+  "type": "object"
+}

changedInput schema / properties / profile / description

Previous value: -"Alias for candidate_profile when reviewing stale queue items."New value: +"Alias for owner_profile when reviewing stale queue items."

Changed2 schema fields changedJul 8, 2026

changedInput schema / properties / candidate_profile / description

Previous value: -"Optional profile used to rescore stale zero-score queue items inside this tenant only."New value: +"Optional profile used to refresh stale zero-score queue items inside this tenant only."

changedInput schema / properties / profile / description

Previous value: -"Alias for candidate_profile when reviewing/rescoring stale queue items."New value: +"Alias for candidate_profile when reviewing stale queue items."

Changed1 schema field changedJun 19, 2026

addedInput schema / properties / hydration_limit

Added value: +{
+  "default": 3,
+  "description": "Bounded live-hydration attempts for thin roles before compose. Reports attempts and remaining needs_role_hydration; never applies or sends.",
+  "maximum": 5,
+  "minimum": 1,
+  "type": "integer"
+}

Changed2 schema fields changedJun 17, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": true,
+  "description": "Return counts, status buckets, mailbox status, and a bounded slate without full bucket payloads. Defaults true for hosted MCP latency.",
+  "type": "boolean"
+}

addedInput schema / properties / section_limit

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

AddedJun 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that mailbox reconciliation runs server-side via the StackFast service-account reader and forbids client-side substitution. The red-receipt stop behavior is a meaningful behavioral trait that is not present in the annotations or schema.

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 information-dense but well structured: it front-loads the verb and object, lists the report components, then gives the critical stop condition. Each of the four sentences earns its place, and the long component list is justified by the tool's broad reporting scope.

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?

Given the output schema exists and the annotations already declare read-only behavior, the description supplies the missing operational context: server-side mailbox reconciliation, no client-side mailbox reads, the stop condition, and the no-sends/no-applications boundary. This is sufficient for an agent to invoke the tool correctly across its 11 parameters.

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 64%, with several parameters already documented such as include_items, hydration_limit, include_applied, and include_archived. The description adds conceptual context by mapping report sections like 'stale/closed rows' and 'bounded needs_role_hydration recovery' to those parameters, but it does not add per-parameter detail beyond 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 opens with a specific verb and resource: 'Return the closed-loop Talent Scout daily operating report from the shared tenant queue' and then enumerates what the report contains. It also distinguishes itself from action-oriented siblings by explicitly stating 'Read-only control-tower view; no sends or applications.'

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 explicit operational guidance: clients must not invoke their own Gmail/email connector, and if mailbox_reconciliation_status is not ok, they should surface the red receipt and stop. It does not name sibling tools to prefer instead, but it provides clear context for when to use this reporting tool and when to halt.

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?