Skip to main content
Glama

workorai

by io.github.work0r-ai

Get candidate

employer.get_candidate

Fetch a discoverable candidate by user id. Returns search-entry shape plus a light interview slice (overallScore + summary + completedAt + evaluatedAt) and existingApplications: every JobApplication this candidate has on any of the employer's jobs (all 4 statuses, all 4 job statuses) so the agent can decide whether re-inviting will succeed. Heavy artefacts (transcript, facts, resume, github, linkedin) live behind employer.get_applicant_detail and require an application.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiKeyNo
userIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
candidateNo

TDQS

A4.1/5.0
Behavior4/5

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

No annotations, so description carries full burden. Discloses return shape (search-entry shape, interview slice, existingApplications), what is not included (heavy artefacts), and purpose of data. Adequately transparent.

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?

Description is fairly concise given the information it conveys. Front-loaded with main action. Every sentence adds value, though slightly long.

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?

Given the presence of an output schema (not shown here) and the description's rich behavioral context (return shape, what's excluded, how to get more), it is complete for the tool's complexity.

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

Parameters2/5

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

Schema description coverage is 0%. Description only mentions userId implicitly and does not describe apiKey. While the description adds rich behavioral context, it adds minimal value for parameter semantics specifically.

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?

Description clearly states 'Fetch a discoverable candidate by user id', specifying verb (fetch), resource (candidate), and scope (by user id). It distinguishes from sibling tools like employer.get_applicant_detail by noting heavy artefacts are elsewhere.

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?

Provides explicit context on when to use this vs. get_applicant_detail (for heavy artefacts). Mentions that existingApplications helps decide re-invitation feasibility, implying a use case. Clear but could more explicitly state alternatives.

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

All workorai toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Every tool in the candidate and employer sets targets a distinct action or resource with no ambiguity. Tools like `search_candidates_by_query` and `search_candidates_for_job` have clearly different purposes, and all other tools perform unique operations.

Naming Consistency5/5

All tools follow a consistent `domain.action` pattern with snake_case action names. The naming is uniform across both candidate and employer tools, using standard verbs like get, list, create, update, delete, search, set, etc.

Tool Count4/5

29 tools cover two distinct user roles (candidate and employer) with separate workflows. While above the typical 3-15 range, each tool serves a specific purpose and the count is justified for a hiring platform's API surface.

Completeness4/5

The tool surface provides comprehensive CRUD and lifecycle operations for jobs, applications, invitations, and candidate searches for both roles. Minor gaps like candidate profile update tools are likely handled outside the MCP server, so the set feels nearly complete.

Resources