Skip to main content
Glama

report_hiring_outcome

Submit the final hiring decision (hired/rejected/withdrawn) for a candidate. Use this to close the loop and help refine the specialized AI models for future accuracy.

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>",
      "candidate_id": "<candidate_id>",
      "outcome": "<outcome>"
    },
    "name": "report_hiring_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job ID.
outcomeYesThe final outcome of the candidate's journey.
candidate_idYesThe candidate ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / candidate_id / description
      Previous value: -"The candidate ID"New value: +"The candidate ID."
    • changedInput schema / properties / job_id / description
      Previous value: -"The job ID the candidate belongs to"New value: +"The job ID."
    • changedInput schema / properties / outcome / description
      Previous value: -"Hiring outcome"New value: +"The final outcome of the candidate's journey."
  2. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses one useful non-obvious fact — the submitted data is used to refine specialized AI models — but says nothing about whether an outcome can be overwritten, whether submission is irreversible, what permissions are required, or what side effects (e.g., notifications) it triggers.

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?

Two tight sentences with the purpose front-loaded and no redundant wording. The second sentence mixes a vague usage phrase ('close the loop') with a genuinely useful data-use note, so it is efficient but not maximally sharp.

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

Completeness3/5

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

The tool is simple, fully required-parameterized, and 100% schema-documented with no output schema, so the description is close to sufficient. However, for an unannotated mutation of a hiring record it should at least state whether the decision is final or amendable.

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%, so all three parameters are already documented, and the description only restates the outcome enum values that appear in the schema. It adds no format or constraint detail beyond the structured fields, so the baseline 3 applies.

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?

States a specific verb and resource ('Submit the final hiring decision') and enumerates the accepted outcome values, so the agent knows exactly what the tool does. It does not name or distinguish itself from any sibling, which keeps it short of a 5.

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

Usage Guidelines3/5

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

'Use this to close the loop' implies the timing (after the hiring process concludes) but gives no explicit preconditions, no when-not guidance, and no alternatives among the many sibling tools. Usage is inferable but not spelled out.

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.

Resources