HireSquire Agent Ecosystem

get_results

Retrieve detailed candidate scores, AI reasoning, and interview questions for a completed job. Only call this once "get_screening_status" returns a "completed" status.

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_results"
  }
}

Input Schema

Name	Required	Description
`job_id`	Yes	The unique ID of the completed screening job.
`min_score`	No	Optional: Minimum score threshold (0-100) to filter results.
`only_top_n`	No	Optional: Limit results to the top N candidates. Defaults to 20 to protect context windows. Max 100.

Output Schema

Name	Required	Description
`has_more`	No	True if there are more candidates than returned.
`candidates`	No
`total_candidates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJun 3, 2026

addedInput schema / properties / only_top_n / default
```
Added value: +20
```

changedInput schema / properties / only_top_n / description

Previous value: -"Optional: Limit results to the top N candidates."New value: +"Optional: Limit results to the top N candidates. Defaults to 20 to protect context windows. Max 100."

addedOutput schema / properties / has_more

Added value: +{
+  "description": "True if there are more candidates than returned.",
+  "type": "boolean"
+}

addedOutput schema / properties / total_candidates
```
Added value: +{
+  "type": "integer"
+}
```

Changed4 schema fields changedMay 16, 2026

changedInput schema / properties / job_id / description

Previous value: -"The unique ID of the screening job."New value: +"The unique ID of the completed screening job."

addedInput schema / properties / min_score / default
```
Added value: +0
```

changedInput schema / properties / min_score / description

Previous value: -"Minimum score threshold (0-100). Only candidates with scores equal to or higher than this value will be returned."New value: +"Optional: Minimum score threshold (0-100) to filter results."

changedInput schema / properties / only_top_n / description

Previous value: -"Limit the results to the top N candidates based on their score."New value: +"Optional: Limit results to the top N candidates."

First observedMay 11, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It discloses the key prerequisite and returned content, but it does not explicitly confirm read-only safety, permissions, rate limits, or pagination/context behavior; the only_top_n context protection appears in the schema, not the description.

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 sentences, with the purpose front-loaded and the gating condition following immediately. There is no unnecessary 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?

For a read tool with a fully described input schema and an output schema, the description covers purpose, returned content, and the prerequisite status condition. It is largely complete, though the absence of annotations leaves minor behavioral gaps.

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 coverage is 100%, and the schema already documents job_id, min_score, and only_top_n with defaults and max values. The description adds only the completed-job context and no additional parameter semantics beyond the schema.

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?

States a specific verb ('Retrieve') and concrete resources (candidate scores, AI reasoning, interview questions) scoped to a completed job. This clearly distinguishes it from a status-check sibling by requiring completed status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says only to call it once get_screening_status returns a completed status, which implies not before completion. It does not name alternative tools such as compare_candidates, but the gating condition is clear.

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?