HireScript MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | Yes | Set your Anthropic API key to enable Claude-powered job description generation and bias analysis. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_job_descriptionA | Generate an inclusive, bias-free job description using AI. Returns the job description text along with a bias score and any warnings about potentially biased language. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name follows a clear verb_noun pattern (generate_job_description).
One tool is too few for a server named 'HireScript MCP Server', which suggests a broader hiring or recruitment domain. A single tool for generating job descriptions feels thin and incomplete for such a scope.
The tool surface is severely incomplete for a hiring domain. It only covers job description generation, with obvious gaps like creating, updating, or managing job listings, candidate tracking, or interview scheduling, which are core to recruitment workflows.