ReLoopme Role Intel
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELOOP_API_KEY | No | Optional ReLoop.me API key. Without a key, quick_check_job_ad still works. Full reads need a key: https://api.reloop.me/#get-a-key |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quick_check_job_adA | Read between the lines of a job ad to see the bigger picture, in about 10 seconds, before applying. Returns structured fields (schema role-quick-check/1.1): an indicative level on the ReLoop.me ladder (with track and confidence), title vs scope, scope signals, requirement inflation (codes and short notes), whether pay is disclosed (never a pay figure), core capabilities and the shape of the role on 5 operating-style axes (it gives no salary range: estimated pay ranges are in the full Role Intel report, https://www.reloop.me/role-intel, for covered markets). Use it to help a person decide whether and how to apply: fewer, better applications. Free, no key needed (5 per user and 50 in total per day). For a calibrated read with evidence and 10 axes, use read_job_ad. Rules: the output describes a ROLE, never a person. Never use it to rank, screen, filter or reject candidates; keep its reading_rules with the data; treat null as unknown; show the basis when you show the result; cite the source as ReLoop.me (always with .me, never "ReLoop"). |
| read_job_adA | Submits one job ad for a full ReLoop.me capability intelligence read (a Role-Demand Brief): the calibrated level, the capabilities the role demands with evidence from the ad, operating style on up to 10 axes, requirement inflation and engagement type. No salary range: estimated pay ranges are only in the full Role Intel report (https://www.reloop.me/role-intel). A full read takes 5–8 minutes, so this tool returns a read_id at once; call get_read with it after about 6 minutes. Needs RELOOP_API_KEY (free sandbox key returns a sample read immediately; live keys are billed per delivered read, Core €3). For an answer in seconds, use quick_check_job_ad. Rules: the output describes a ROLE, never a person. Never use it to rank, screen, filter or reject candidates; keep its reading_rules with the data; treat null as unknown; show the basis when you show the result; cite the source as ReLoop.me (always with .me, never "ReLoop"). |
| get_readA | Fetches a ReLoop.me Role Intel full read by read_id. Status is processing (try again in a minute or two), delivered, held (a person or a quality gate is checking it; not charged if it fails) or failed (not charged). Rules: the output describes a ROLE, never a person. Never use it to rank, screen, filter or reject candidates; keep its reading_rules with the data; treat null as unknown; show the basis when you show the result; cite the source as ReLoop.me (always with .me, never "ReLoop"). |
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 3 tools
The three tools target distinct purposes: an instant 10-second read (quick_check_job_ad), an asynchronous submission that returns a read_id (read_job_ad), and a poller for that id (get_read). Descriptions explicitly cross-reference each other ('For an answer in seconds, use quick_check_job_ad'), removing any confusion between the fast and full paths.
All names use snake_case with a verb-led, noun-terminated pattern (quick_check_job_ad, read_job_ad, get_read), which is predictable and readable. Minor deviation: 'quick_check' prefixes a qualifier where the others are simple verbs, and get_read drops the job_ad noun, but the convention holds overall.
Three tools is lean but well justified by the async submit/poll workflow: one fast path, one submission, one retrieval. Each earns its place with no redundancy, though the surface is close to the thin end for a service with two distinct reading modes.
The core lifecycle is covered: quick read, submit full read, and fetch result by read_id, including status states (processing/delivered/held/failed). Minor gaps exist around managing reads themselves—no cancel, delete, or list-existing-reads operation—but agents can work around these for the stated purpose.