Semata

Create role from job description

create_role_from_jd

Create a role and its empty screening from the original pasted text, PDF, or public job-posting URL. The complete original is saved separately from the role summary and screening criteria. Pass exactly one source. Requires OAuth or a scoped token, and workspace write permission.

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": "create_role_from_jd"
  }
}

Input Schema

Name	Required	Description
`url`	No
`text`	No
`filename`	No
`pdfBase64`	No
`workspaceId`	Yes	The workspace id returned by list_workspaces. Use 'personal' for the personal workspace.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (which mark it non-read-only, non-destructive, open-world), the description adds real context: the original text is persisted separately from the generated role summary and screening criteria, and OAuth/scoped token plus workspace write permission are required. It stops short of noting any side effects such as duplicate creation or rate limits.

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?

Three short sentences, front-loaded with the action and resource, then data-handling behavior, then the input constraint and auth requirement. Nothing is redundant or padded.

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

Completeness3/5

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

For a 5-parameter mutation tool with no output schema and only 20% schema coverage, the description covers auth and source exclusivity but leaves notable gaps: how the PDF path works (filename/pdfBase64 pairing), and what the caller receives back after the role and empty screening are created.

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 only 20% (only workspaceId is documented inline), so the description must carry the load; it does clarify that exactly one of the source inputs is expected. It does not explain the role of filename or that pdfBase64 likely pairs with it, leaving two of five parameters under-explained.

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 ('Create a role and its empty screening') plus the accepted input sources (text, PDF, URL), which is more precise than a bare 'create'. It does not explicitly distinguish itself from the sibling create_role or parse_job_description, so an agent must infer the difference from the source-based framing.

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?

The constraint 'Pass exactly one source' is a genuine usage rule, and the auth/permission prerequisites are stated. However, there is no guidance on when to pick this tool over create_role or parse_job_description, which are the obvious alternatives given the sibling list.

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?