HireSquire Agent Ecosystem

get_screening_status

Check the processing status and progress of a screening job. Use this to poll for completion after calling "create_screening" if a webhook was not provided.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "<job_id>"
    },
    "name": "get_screening_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	The unique ID returned by create_screening.

Output Schema

Name	Required	Description	Default
`status`	No	Current status: processing, completed, or failed.
`progress`	No	Percentage of completion (0-100).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 16, 2026

changedInput schema / properties / job_id / description

Previous value: -"The unique ID of the job to check."New value: +"The unique ID returned by create_screening."

removedInput schema / properties / job_id / examples
```
Removed value: -[
-  12345
-]
```

First observedMay 11, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations supplied, the description carries the burden of behavioral disclosure. It usefully discloses that this is a polling tool used after create_screening when no webhook exists, but it does not mention rate limits, authentication requirements, retry expectations, or what a completed versus failed status looks like.

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?

The definition is two concise sentences. It is front-loaded with the core purpose and then adds the key usage condition without any wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has one required parameter, and includes an output schema, so the description does not need to explain return values in detail. It covers purpose and polling context well, though it could say slightly more about error or status handling if those are not captured by the output schema.

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

Parameters3/5

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

Schema description coverage is 100%, and the single job_id parameter is already documented as the unique ID returned by create_screening. The description adds no additional meaning about job_id beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: check the processing status and progress of a screening job. It is clear what the tool does and ties naturally to create_screening, though it does not explicitly distinguish itself from all related siblings such as get_results or audit_screening_job.

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?

It explicitly says to use the tool to poll for completion after calling create_screening if a webhook was not provided. That gives both the triggering condition and the alternative scenario, leaving little ambiguity about when to invoke it.

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

All HireSquire Agent Ecosystem tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?