Hire or Automate

Split a role into AI and human work

split_role

Read-onlyIdempotent

Use this when the user wants to split a whole job into work AI can do now, work AI drafts for approval, and work that needs a person. Best for: "which tasks of a bookkeeper need a person?", "split a software engineer role" or "job ad and two-week trial for a restaurant cook". Returns: the ONET occupation, each task tagged ai_now, ai_draft or human with rule and reason, a job-ad skeleton for the human tasks, and a two-week trial. Input tips: send title, a job title such as "bookkeeper" or an ONET-SOC code such as "15-1252.00". The title alone is best. Add description only when the title is vague; it widens the word match and can lower precision. Set occupations to 2 or 3 only to expand more than one match. Not for: one named task (answer it plainly), judging a person, reading a resume, or legal or pay advice. If status is no_match, ask for a clearer title or an O*NET code; do not invent tasks. If personal_data, ask again without contact details. If not_ready, retry later.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "bookkeeper"
    },
    "name": "split_role"
  }
}

Input Schema

Name	Required	Description
`title`	No	A job title, such as "bookkeeper", or an O*NET-SOC code in the form NN-NNNN.NN, such as "15-1252.00". Preferred input. No names, emails or phone numbers.
`description`	No	Optional pasted job description, for when the title is vague or missing. It widens the word match, so it can lower precision. Not stored. No names, emails or phone numbers.
`occupations`	No	How many matching occupations to expand, 1 to 3. Default 1. Further matches are listed as codes and titles only.

Output Schema

Name	Required	Description
`also`	No	Other matches not expanded.
`note`	No	Reminder that the split is a planning aid, not a decision about any person.
`as_of`	Yes	ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.
`match`	No	How the occupation was chosen.
`query`	No	What was asked. The description text itself is never echoed.
`trial`	No	Two-week trial template.
`job_ad`	No	Skeleton for the human pile. Empty responsibilities means do not hire for the listed tasks.
`rubric`	No	The rubric rules, first match wins.
`source`	Yes	Who the data comes from, to cite and to check it against.
`status`	Yes	ok, or why there is no split.
`message`	No	Set when status is not ok, with the next step. no_match: send a clearer title or an O*NET code. not_ready: retry later. personal_data: resend without names, emails or phone numbers.
`occupations`	No	Matching occupations with each task tagged ai_now, ai_draft or human.
`rubric_version`	No	Version of the fixed rubric that tagged the tasks.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "title": "bookkeeper"
+  }
+]

addedOutput schema / properties / as_of

Added value: +{
+  "description": "ISO 8601 time the data was published by its source or fetched from it. A cached answer keeps the time of its fetch.",
+  "type": "string"
+}

changedOutput schema / properties / source / description

Previous value: -"Data source and license to credit in the answer."New value: +"Who the data comes from, to cite and to check it against."

removedOutput schema / properties / source / properties / as_of
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / source / properties / attribution

Removed value: -{
-  "description": "Credit line to include in the answer.",
-  "type": "string"
-}

removedOutput schema / properties / source / properties / license
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / source / properties / license_url
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / source / properties / publisher
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / source / properties / release
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / source / required
```
Added value: +[
+  "name",
+  "url"
+]
```

changedOutput schema / required

Previous value: -[
-  "status"
-]New value: +[
+  "status",
+  "as_of",
+  "source"
+]

Changed20 schema fields changedOct 10, 2026

changedInput schema / properties / description / description

Previous value: -"Optional job description, used only when the title is ambiguous. Not stored. Do not include names, emails or phone numbers."New value: +"Optional pasted job description, for when the title is vague or missing. It widens the word match, so it can lower precision. Not stored. No names, emails or phone numbers."

changedInput schema / properties / title / description

Previous value: -"A job title, or an O*NET-SOC code such as 15-1252.00. Do not include a person's name, email or phone number."New value: +"A job title, such as \"bookkeeper\", or an O*NET-SOC code in the form NN-NNNN.NN, such as \"15-1252.00\". Preferred input. No names, emails or phone numbers."

addedOutput schema / properties / also / items

Added value: +{
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "title"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / job_ad / properties

Added value: +{
+  "approve_before_sending": {
+    "description": "Tasks AI drafts for a person to approve.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "disclaimer": {
+    "type": "string"
+  },
+  "not_this_role": {
+    "description": "Tasks AI can do now.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "responsibilities": {
+    "description": "Human-pile tasks to hire for.",
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "summary": {
+    "type": "string"
+  },
+  "title": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / match / description

Previous value: -"How the occupation was chosen: code, occupation_title, alternate_title, tokens or model."New value: +"How the occupation was chosen."

addedOutput schema / properties / match / properties

Added value: +{
+  "confidence": {
+    "enum": [
+      "high",
+      "medium",
+      "low"
+    ],
+    "type": "string"
+  },
+  "matched_on": {
+    "description": "The O*NET title that matched, when a title matched.",
+    "type": "string"
+  },
+  "method": {
+    "enum": [
+      "code",
+      "occupation_title",
+      "alternate_title",
+      "tokens",
+      "model",
+      "none"
+    ],
+    "type": "string"
+  },
+  "model": {
+    "description": "Whether a language model broke a tie.",
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "note": {
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "used",
+          "skipped"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  }
+}

addedOutput schema / properties / message / description

Added value: +"Set when status is not ok, with the next step. no_match: send a clearer title or an O*NET code. not_ready: retry later. personal_data: resend without names, emails or phone numbers."

addedOutput schema / properties / note / description

Added value: +"Reminder that the split is a planning aid, not a decision about any person."

addedOutput schema / properties / occupations / items

Added value: +{
+  "properties": {
+    "code": {
+      "description": "O*NET-SOC code, such as 15-1252.00.",
+      "type": "string"
+    },
+    "counts": {
+      "properties": {
+        "ai_draft": {
+          "type": "integer"
+        },
+        "ai_now": {
+          "type": "integer"
+        },
+        "human": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "ai_now",
+        "ai_draft",
+        "human"
+      ],
+      "type": "object"
+    },
+    "description": {
+      "type": "string"
+    },
+    "tasks": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "O*NET task id.",
+            "type": "string"
+          },
+          "pile": {
+            "description": "ai_now, ai_draft (AI drafts, a person approves) or human.",
+            "enum": [
+              "ai_now",
+              "ai_draft",
+              "human"
+            ],
+            "type": "string"
+          },
+          "reason": {
+            "description": "One-line reason for the pile.",
+            "type": "string"
+          },
+          "rule": {
+            "description": "Id of the rubric rule that tagged the task.",
+            "type": "string"
+          },
+          "text": {
+            "description": "The O*NET task statement.",
+            "type": "string"
+          },
+          "type": {
+            "description": "O*NET task type, such as Core or Supplemental.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "text",
+          "pile",
+          "rule",
+          "reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "description": "O*NET OnLine page for the occupation.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "title",
+    "url",
+    "tasks",
+    "counts"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / query / description

Added value: +"What was asked. The description text itself is never echoed."

addedOutput schema / properties / query / properties

Added value: +{
+  "code": {
+    "description": "The O*NET-SOC code read from the title, if any.",
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "described": {
+    "description": "true when a description was sent.",
+    "type": "boolean"
+  },
+  "title": {
+    "type": [
+      "string",
+      "null"
+    ]
+  }
+}

addedOutput schema / properties / rubric / description

Added value: +"The rubric rules, first match wins."

addedOutput schema / properties / rubric / items

Added value: +{
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "pile": {
+      "enum": [
+        "ai_now",
+        "ai_draft",
+        "human"
+      ],
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "pile",
+    "reason"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / rubric_version / description

Added value: +"Version of the fixed rubric that tagged the tasks."

addedOutput schema / properties / source / description

Added value: +"Data source and license to credit in the answer."

addedOutput schema / properties / source / properties

Added value: +{
+  "as_of": {
+    "type": "string"
+  },
+  "attribution": {
+    "description": "Credit line to include in the answer.",
+    "type": "string"
+  },
+  "license": {
+    "type": "string"
+  },
+  "license_url": {
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "publisher": {
+    "type": "string"
+  },
+  "release": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / status / description

Previous value: -"ok, no_match, not_ready or personal_data."New value: +"ok, or why there is no split."

addedOutput schema / properties / status / enum

Added value: +[
+  "ok",
+  "no_match",
+  "not_ready",
+  "personal_data"
+]

addedOutput schema / properties / trial / properties

Added value: +{
+  "note": {
+    "type": "string"
+  },
+  "pass_if": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "title": {
+    "type": "string"
+  },
+  "week_1": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "week_2": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "status"
+]
```

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description goes further by disclosing the terminal status values (no_match, personal_data, not_ready) and prescribing recovery actions for each, which an agent could not infer from annotations. It does not cover latency, rate limits, or cost, keeping it just below the top.

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?

Front-loaded with the trigger, then cleanly labeled blocks (Best for, Returns, Input tips, Not for, status handling), so it scans well. It is somewhat long, and the Input tips block largely restates the precision caveat already present in the schema's description and occupations field, which is the only real waste.

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?

An output schema exists, yet the description still gives a one-line preview of what comes back (occupation, per-task tags with rule and reason, job-ad skeleton, two-week trial) plus the failure-state branches. For a three-param, zero-required, open-world tool, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds prioritization guidance not in the schema — "the title alone is best" and to add description only when the title is vague because it widens the match and lowers precision, plus "set occupations to 2 or 3 only to expand more than one match." That is real decision value beyond the field docs, though it partially echoes the schema wording.

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?

States a specific verb and resource (split a role/job) and immediately enumerates the three output buckets (ai_now, ai_draft, human), which is the tool's distinctive behavior. Concrete example phrasings (bookkeeper, software engineer, restaurant cook) make it unmistakable versus siblings like submit_feedback.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit positive trigger ("Use this when the user wants to split a whole job"), named exemplar queries, and a hard "Not for" list ruling out single tasks, person judgments, resumes, and legal/pay advice. Alternatives are effectively named by telling the agent to answer one named task plainly instead of calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hire or Automate 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.