Synthire
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_workersB | Search the Workday worker population by name to find a template worker. Returns candidate matches (employee_id, name, job_profile, country) for the user to disambiguate between if more than one comes back. |
| get_worker_templateA | Fetch the confirmed template worker's cloneable fields via Get_Workers. Call this only after the user has confirmed exactly which worker (by employee_id) to use as the template -- it returns the job profile, supervisory org, and country that a new hire will be cloned from. |
| generate_synthetic_identityA | Generate a fresh synthetic first name, last name, and email. Use this to give the new hire its own identity instead of literally
duplicating the template worker's name. |
| synthesize_test_hireA | Submit the user-approved hire payload to the tenant via Hire_Employee. Only call this after the user has explicitly confirmed the proposed
fields -- this is the one tool in this server that actually mutates the
tenant. |
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 4 tools
Each tool occupies a distinct stage of a clear pipeline: search candidates, fetch a confirmed template's cloneable fields, generate a synthetic identity, and submit the hire payload. The descriptions explicitly note sequencing ('call this only after...'), leaving no overlap between them.
All four tools follow a consistent snake_case verb_noun convention (search_workers, get_worker_template, synthesize_test_hire, generate_synthetic_identity). The differing verbs (search/get/synthesize/generate) accurately reflect distinct actions rather than introducing inconsistency.
Four tools is on the lean side but each earns its place in the create-a-test-hire workflow. It fits the narrow scope well, though one or two more (e.g. cleanup) could round it out.
The search-to-hire path is fully covered end to end. The only notable gap is teardown/cleanup of a hired test worker or updating it afterward, which agents may need for repeated test runs.