Skip to main content
Glama

Recruiting Offer Backsolve

bpj_recruiting_offer_backsolve
Read-onlyIdempotent

Work back from target starts through attendance, acceptance and final-interview offer rates, rounding each stage to whole people.

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": {
      "offers": "<offers>",
      "starts": "<starts>",
      "accepts": "<accepts>",
      "finalists": "<finalists>"
    },
    "name": "bpj_recruiting_offer_backsolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
offersYes
startsYes
acceptsYes
finalistsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description does add one genuine behavioral detail beyond the annotations: each stage is rounded to whole people, which matters for interpreting results. It says nothing about how rounding propagates across stages or what the output looks like, so it is useful but thin for a pure calculation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with no filler, front-loaded on the core operation and ending with the rounding caveat. Nothing is redundant, though the stage list could have been aligned to the actual parameter names at no extra cost.

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

Completeness1/5

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

With four required, confusingly titled parameters, 0% schema description coverage and no output schema, the description should clarify parameter identity and return shape. Instead it leaves the naming mismatch (offers vs. target starts) unresolved and names a stage that does not exist as a parameter, so an agent cannot reliably map inputs.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden and only partly meets it. It maps loosely onto 'target starts ... acceptance and final-interview offer rates', but introduces a stage ('attendance') that has no corresponding parameter and never resolves the misleading schema titles, where 'offers' is actually target starts and 'starts' is actually the start rate among acceptances.

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 gives a specific verb ('work back from target starts') and names the three rate stages it inverts, so an agent can tell this is a reverse funnel calculation rather than a forward projection. It does not name the closest sibling, bpj_funnel_backsolve, so the boundary between the two is left implicit.

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

Usage Guidelines2/5

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

There is no statement of when this tool should be chosen, no prerequisites, and no alternative named. The only usage signal is the implicit 'if you have target starts and stage rates' framing, which an agent must infer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.