StackFast FractWin Expert Brain

Talent Scout Role Review

talent_scout_score_fit

Read-onlyIdempotent

Compare a role text with the account owner's own saved preferences using a deterministic checklist so Robert can decide whether to review or apply manually. Returns transparent self-review data; no outbound action.

Input Schema

TableJSON Schema

Name	Required	Description
`target`	No	Structured role text or object.
`profile`	No	Optional owner profile. Defaults to Robert's safe Talent Scout profile for public connector smoke tests.
`tenant_id`	No
`target_text`	No	Plain-language target role text for lightweight connector smoke tests.
`owner_profile`	No	Alias for profile.
`min_review_threshold`	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.

AddedJul 21, 2026
RemovedJul 9, 2026

Changed1 schema field changedJul 8, 2026

changedInput schema / properties / profile / description

Previous value: -"Optional candidate/operator profile. Defaults to Robert's safe Talent Scout profile for public connector smoke tests."New value: +"Optional owner profile. Defaults to Robert's safe Talent Scout profile for public connector smoke tests."

Changed5 schema fields changedJun 17, 2026

addedInput schema / properties / candidate_profile

Added value: +{
+  "description": "Alias for profile.",
+  "type": "object"
+}

addedInput schema / properties / profile / description

Added value: +"Optional candidate/operator profile. Defaults to Robert's safe Talent Scout profile for public connector smoke tests."

addedInput schema / properties / target / description
```
Added value: +"Structured target opportunity."
```

addedInput schema / properties / target_text

Added value: +{
+  "description": "Plain-language target role text for lightweight connector smoke tests.",
+  "type": "string"
+}

removedInput schema / required

Removed value: -[
-  "profile",
-  "target"
-]

AddedJun 9, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds valuable behavioral context beyond that: it is deterministic, returns self-review data, and takes no outbound action. The 'no outbound action' clarification is especially useful for an agent deciding whether invocation has side effects.

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 two concise sentences, front-loads the main purpose and decision context, and then states the safety/return behavior. Every clause earns its place and there is no filler.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the annotations, output schema, and relatively rich input schema, the description is mostly complete: it gives purpose, decision context, deterministic behavior, return nature, and side-effect safety. It does not clarify how this tool relates to the closely named sibling talent_scout_role_review, but the structured fields cover the remaining invocation details.

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 67%, so the input schema carries most parameter meaning. The description loosely maps to target/target_text ('role text') and profile/owner_profile ('account owner's saved preferences'), but it adds little insight about min_review_threshold or tenant_id. This meets the baseline for schema-covered parameters without strongly compensating for uncovered ones.

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 action: compare a role text against the account owner's saved preferences using a deterministic checklist, and it frames the output as transparent self-review data for Robert's manual decision. It does not explicitly differentiate from closely related siblings like talent_scout_role_review or talent_scout_explain_preferences_match, so it stops short of a 5.

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 a clear use context: the agent should call this when Robert needs to decide whether to review or apply manually. It does not name alternatives or state when not to use the tool, but the intended scenario is reasonably explicit.

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?