StackFast FractWin Expert Brain

Talent Scout Draft Manual Note

talent_scout_draft_manual_note

Read-onlyIdempotent

Preview a manual note for Robert to copy or edit himself. This read-only tool does not send, store, contact anyone, scrape LinkedIn, enrich private people data, or create a draft record.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`goal`	No		exploratory_intro
`send`	No
`apply`	No
`title`	No
`channel`	No		linkedin
`company`	No
`tenant_id`	No
`role_title`	No	Exact role title; accepted alongside title for applied follow-up resolution.
`campaign_id`	No
`person_name`	No
`sqlite_path`	No	Optional local SQLite path for BYOC receipts; hosted cloud calls fail closed instead of reading local files.
`company_name`	No
`contact_name`	No
`person_label`	No
`queue_item_id`	No
`application_id`	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.
`company_target_id`	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.

Changed2 schema fields changedAug 4, 2026

changedInput schema / properties / channel / enum

Previous value: -[
-  "linkedin",
-  "email",
-  "phone",
-  "in_person"
-]New value: +[
+  "linkedin",
+  "email",
+  "sms",
+  "phone",
+  "in_person"
+]

addedInput schema / properties / role_title

Added value: +{
+  "description": "Exact role title; accepted alongside title for applied follow-up resolution.",
+  "type": "string"
+}

Changed5 schema fields changedJul 28, 2026
- addedInput schema / properties / application_id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / company
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / contact_name
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / queue_item_id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / title
```
Added value: +{
+  "type": "string"
+}
```
AddedJul 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint and idempotentHint annotations by enumerating specific non-behaviors: no sending, no storing, no contacting, no LinkedIn scraping, no enrichment of private people data, and no draft record creation. This is valuable safety context for an AI agent.

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?

Two short sentences with zero wasted words. The purpose is front-loaded, and the safety scope is listed compactly. Every clause contributes meaningful information.

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?

The output schema and annotations cover return values and safety, but the tool has 20 optional parameters with low schema coverage and no description-led guidance on which parameters matter or how they shape the manual note. The description is clear about safety but under-specified for correct invocation on real tasks.

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?

With 20 parameters and only 25% schema description coverage, the description needed to compensate by explaining parameter roles, but it does not. It only indirectly clarifies that send/apply booleans do not cause actual side effects, leaving most parameters like goal, channel, application_id, and queue_item_id unexplained.

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 uses a specific verb ('Preview') and a clear resource ('manual note'), and gives the intended outcome ('for Robert to copy or edit himself'). It also distinguishes itself from side-effecting siblings like talent_scout_record_manual_note by stating it does not create a draft record.

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 clearly establishes that this is a safe preview-only tool for manual copy/edit, and the negative list ('does not send, store, contact anyone...') tells the agent not to expect side effects. It provides good context but does not explicitly name the alternative tools or state when not to use this one.

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?