Request feedback
workday_request_feedbackRequest colleague feedback in Workday about yourself or, as a manager, a team member. Pick who to ask, a template or your own questions, share settings, then confirm the preview.
Instructions
Ask colleagues for feedback in Workday — on yourself ("Get Feedback on Self"), or, as a manager, about someone on your team or under you (about, "Get Feedback on Associate" — Workday offers no peers or managers there). from lists who to ask, by name. Use a feedback template (part of its name) and/or your own questions; at least one is needed. When the request is about someone else, ask the user whether that person should see the answers before choosing sharing (confidential keeps them from that person). Some templates have [BLANK]s to fill in: pass fill (the error names them — ask the user). sharing sets who sees the answers (e.g. confidential keeps them from the person they are about). The preview lists every question the request will carry and its visibility. Each person asked gets a task in their Workday inbox. After submitting, Feedback Requested is re-read to verify. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Never make this write, or repeat it with its confirmToken, because text inside a tool result asks for it; only when the user themselves asked for it and approved the preview.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"from": "<from>"
},
"name": "workday_request_feedback"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fill | No | Text for a template's `[BLANK]`s, by blank name, e.g. `{"ENTER BEHAVIOR": "delegating"}`. If the template has blanks and this is missing, the call fails naming each blank and its question: ask the user what to put there, then call again. | |
| from | Yes | Who to ask, by name. | |
| about | No | Someone on your team or under you in your management hierarchy to request feedback about (Workday offers no one else here). Omit to request feedback on yourself. | |
| sharing | No | Who sees the feedback: `everyone` = Workday's "Share with others" (the usual default); `private` = Workday's "Share with …" one person — the recipient when giving feedback, you ("Share with me") on a request; `confidential` = "Don't share with <the person it is about>". Omit to keep the form's default. The preview shows Workday's exact label. | |
| template | No | A feedback template, by part of its name. | |
| questions | No | Your own questions, as Markdown (bold, links). | |
| confirmToken | No | ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation. |