Semata

Create role

create_role

Create a role and its empty screening in the selected workspace. Needs a name and a seniority range in years (0 to 20, minimum not above maximum); a description, target archetypes, up to 7 key requirements, industry experience, company stage and a location are optional. Adds a new record and changes nothing that exists. Retrying the same request returns the role it already created. Requires OAuth or a scoped token and a workspace role that can edit.

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": {
      "workspaceId": "<workspaceId>",
      "name": "<name>",
      "seniority_min": "<seniority_min>",
      "seniority_max": "<seniority_max>"
    },
    "name": "create_role"
  }
}

Input Schema

Name	Required	Description
`name`	Yes
`description`	No
`workspaceId`	Yes	The workspace id returned by list_workspaces. Use 'personal' for the personal workspace.
`company_stage`	No
`location_city`	No
`seniority_max`	Yes
`seniority_min`	Yes
`key_requirements`	No
`location_country`	No
`target_archetypes`	No
`industry_experience`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing idempotency ('retrying the same request returns the role it already created'), the exact mutation footprint ('adds a new record and changes nothing that exists'), and the auth/permission prerequisites. This is precisely the context annotations cannot express.

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?

Four sentences, front-loaded with the action and its side effect, then required fields, then behavior, then auth. Dense but every clause carries information; the parenthetical bounds are the only mildly redundant part since the schema also enforces them.

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?

For an 11-parameter mutation tool with no output schema, it covers enough: required inputs, validation rules, mutation footprint, idempotency, and permissions. What's missing is any indication of what is returned (the role, the screening id) and differentiation from create_role_from_jd.

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?

With only 9% schema description coverage, the description carries the load well: it names the required fields, states the 0-20 bounds and the min-not-above-max constraint, and characterizes the optional fields including the cap of 7 key requirements. It omits the workspaceId semantics and the required name/description shape of target_archetypes objects, so not quite a 5.

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?

States a specific verb and resource plus a non-obvious side effect: it also creates the role's empty screening. It does not distinguish itself from siblings like create_role_from_jd or duplicate_role, so an agent cannot tell from the description alone which creation path to take.

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

Usage Guidelines3/5

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

Context is implied by 'in the selected workspace' and prerequisites are given ('Requires OAuth or a scoped token and a workspace role that can edit'), but there is no explicit guidance on when to choose this over create_role_from_jd, which is the obvious sibling alternative for creating a role.

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

All Semata 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?