HireSquire Agent Ecosystem

estimate_screening_cost

Calculate the exact credit cost for a planned screening job based on candidate count. Use this as a pre-flight check before calling "create_screening".

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": {
      "candidate_count": "<candidate_count>"
    },
    "name": "estimate_screening_cost"
  }
}

Input Schema

Name	Required	Description	Default
`candidate_count`	Yes	Number of resumes you intend to screen.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 16, 2026
- changedInput schema / properties / candidate_count / description
```
Previous value: -"Number of candidates to screen"New value: +"Number of resumes you intend to screen."
```
- addedInput schema / properties / candidate_count / minimum
```
Added value: +1
```
First observedMay 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: 'Calculate' and 'pre-flight check' signal a non-mutating estimation with no credit deduction. It does not explicitly state that no credits are consumed or whether the estimate is guaranteed to match the eventual charge, which leaves a modest gap for a cost-quoting tool.

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 short sentences, zero filler, with the purpose stated first and the call-to-action sequencing second. Every sentence earns its place.

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 one-parameter, non-destructive estimation tool this is nearly complete; the caller knows what it computes and when to call it. Since there is no output schema, a brief note on the return shape (e.g. a credit total, possibly with a breakdown) would have closed the remaining gap.

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 single parameter is documented as 'Number of resumes you intend to screen.' The description adds only the equivalence between 'candidate count' and the screening input; the minimum:1 constraint and integer type already live in the schema. Baseline 3 is appropriate.

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?

Specific verb 'Calculate' plus a precisely scoped resource: credit cost for a planned screening job, keyed to candidate count. It is clearly distinct from siblings like get_credit_balance (current balance) or create_screening (execution), without needing to open either schema.

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?

It names an explicit trigger ('pre-flight check before calling create_screening') and the sibling it precedes, which is exactly the routing an agent needs. There is no explicit 'do not use this for X' exclusion (e.g. for checking current balance), so it falls short of full 5-level guidance.

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?