Skip to main content
Glama

Yardstick ATS

Read the hiring manager decision

yardstick_applications_hiring_step_decision
Read-onlyIdempotent

Read where the hiring manager's decision stands on the candidate's latest step that waits on one: advanced, held, waiting, or none. Only the job's recruiter or hiring manager, organization admins and whoever may decide the step can see the decision; anyone else reads none.

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": {
      "application_id": "<application_id>"
    },
    "name": "yardstick_applications_hiring_step_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idNo
application_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the bar is lower. The description adds valuable behavioral context: only specific roles can see the decision, unauthorized users receive 'none', and the possible decision states are disclosed.

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 description is two tight sentences with no wasted wording. The core purpose and returned states are front-loaded before the permission caveat.

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 description covers the decision states and visibility behavior well, which is useful because there is no output schema. However, with 0% schema description coverage, the unexplained parameters leave the definition incomplete for an agent trying to call it correctly.

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%, and the description does not mention either application_id or request_id. It implies a candidate/application context but does not explain the identifier parameter or what the optional request_id is for, leaving a significant parameter gap.

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?

The description uses the specific verb 'Read' and clearly names the resource: where the hiring manager's decision stands on the candidate's latest step. It also enumerates the possible outcomes (advanced, held, waiting, none), making the tool's purpose distinct from decision-making siblings.

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?

The description makes clear this is a status-reading tool and explains role-based visibility, but it does not explicitly name the decide sibling or state when to use this read instead of yardstick_applications_decide_hiring_step. The context is clear, but alternative routing is left implicit.

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.