Semata

Set candidate rating

set_candidate_rating

Destructive

Set the recruiter rating on one candidate: favourite, approved, review or gated, replacing any earlier rating. Rating a candidate gated also archives them, so they leave the active shortlist; the other ratings leave the candidate where they are. Use bulk_triage_candidates to rate several at once. This is advice for the team, not a hiring decision; use record_hiring_outcome to record one. 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>",
      "candidateId": "<candidateId>",
      "rating": "<rating>"
    },
    "name": "set_candidate_rating"
  }
}

Input Schema

Name	Required	Description
`rating`	Yes
`candidateId`	Yes
`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

A4.7/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing that the rating replaces any earlier rating, that 'gated' also archives the candidate and removes them from the active shortlist, and that OAuth or a scoped token plus an edit-capable workspace role is required. That is concrete side-effect and permission context the destructiveHint/readOnlyHint flags cannot convey.

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?

Front-loads the action and values in the first clause, then adds side effects, alternatives, and auth in tight sentences with no filler. Every sentence carries distinct information.

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?

For a small three-parameter mutation with no output schema, the description covers side effects (replacement, archiving), permission requirements, and sibling alternatives—everything needed to invoke it correctly.

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 only 33% (only workspaceId is documented inline), but the description compensates by enumerating the rating values and explaining the semantic effect of 'gated' versus the others. candidateId is left implicit, though its meaning is self-evident from the description.

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?

Names a specific verb (set) and resource (recruiter rating on one candidate) and enumerates the exact rating values, so the agent knows precisely what changes. It is clearly distinguished from record_hiring_outcome and bulk_triage_candidates.

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?

Explicitly routes the agent: use bulk_triage_candidates to rate several at once, and record_hiring_outcome to record an actual hiring decision. It also notes the ratings are team advice, not a hiring decision, giving a clear when-not signal.

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?