Skip to main content
Glama

workorai

by io.github.work0r-ai

Decline invitation

candidate.decline_invitation

Decline an employer's invitation to a job (INVITED -> DECLINED). TERMINAL — a declined invite blocks any re-invite from the employer, so only decline when the candidate is sure. Idempotent (declining again succeeds). Returns NOT_INVITED when there is no open invitation, NOT_FOUND when the job/invite is not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobIdYes
apiKeyNoOptional WorkorAI MCP key for in-session authentication when the MCP client was initialized anonymously.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
statusNo

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses the terminal nature, idempotency, and error scenarios. The behavioral traits are clearly communicated.

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?

Two concise sentences that front-load the action and state transition. Every sentence adds essential information with no wasted words.

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, the description covers all necessary aspects: purpose, state change, terminal consequence, idempotency, and error returns. It is complete for an agent to decide when and how to invoke.

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?

The schema covers 50% of parameters (apiKey has description, jobId does not). The description does not explicitly describe jobId but adds semantic context about state change and terminal behavior that helps agents understand parameter usage.

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?

The description uses a specific verb ('Decline') and clearly indicates the state transition (INVITED -> DECLINED). It distinguishes from siblings like 'accept_invitation' by focusing on the decline action.

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 warns that declining is terminal and blocks re-invites, advising to only decline when sure. Also notes idempotency and describes typical error returns, guiding appropriate use.

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