Semata

List roles

list_roles

Read-only

List the roles in the selected Semata workspace. Each role represents one hiring need and owns exactly one screening list of candidates. Call this to see what the user is hiring for, or to resolve a role name to its id before calling the role detail tool.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum roles to return.
`offset`	No	Number of roles to skip.
`workspaceId`	Yes	The workspace id returned by list_workspaces. Use 'personal' for the personal workspace.
`includeClosed`	No	Include archived roles as well as active ones. Defaults to active only.

Output Schema

Name	Required	Description	Default
`code`	No
`error`	No
`limit`	No
`roles`	No
`total`	No
`offset`	No
`workspaceId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful model context — one role maps to exactly one screening list — but says nothing beyond the schema about pagination ceilings or that archived roles are excluded by default.

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, then the domain model, then the call-to-action. Every sentence carries information an agent cannot get from the schema alone.

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?

With annotations, a full-coverage input schema and an output schema, the description need not explain return values. It is complete enough to invoke correctly; only a nudge about paging or that closed roles are hidden by default is missing, and the schema covers both.

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 coverage is 100% and every parameter (workspaceId, limit, offset, includeClosed) carries its own description, so the baseline of 3 applies. The description adds only indirect signal, implying the response contains role names and ids for resolution, without explaining limit/offset or the includeClosed toggle.

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?

Specific verb+resource ("List the roles") scoped to the selected workspace, plus a one-line domain definition ("Each role represents one hiring need and owns exactly one screening list of candidates") that no sibling provides. It distinguishes itself from get_role by casting itself as the resolution step before the role detail tool.

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?

Explicitly names two use cases: browsing what the user is hiring for, and resolving a role name to an id before calling the role detail tool. That is genuine when-to-use guidance with an alternative (get_role) implied, though it never states when NOT to use it and ignores the nearby list_review_roles sibling.

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?