Skip to main content
Glama
Sign In
100Hires MCP Server

100Hires MCP Server

Official
by 100Hires
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

hires_update_application

Update an application's pipeline stage, disqualification status, or CV attachment. Use for general edits; for explicit stage moves, prefer the dedicated move/advance tools.

Instructions

Update application fields such as stage, disqualification flag, and CV. For explicit stage transitions prefer hires_move_application or hires_advance_application.

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": {
      "id": "<id>"
    },
    "name": "hires_update_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
cvNoReplace or attach a CV.
idYesApplication ID.
includeNoComma-separated relations to embed: candidate, cv.text.
stage_idNoMove application to this pipeline stage.
is_disqualifiedNoSet to true to disqualify the candidate on this application.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/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 burden of behavioral disclosure. It mentions updating stage, disqualification, and CV, but does not disclose side effects such as whether disqualification triggers notifications, whether CV replacement is irreversible, or any authorization requirements. The description adds little beyond what the schema already states, leaving significant behavioral ambiguity.

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 compact and well-structured: the first sentence states the core functionality with examples, and the second sentence gives a clear pointer to alternatives. Every word earns its place, with no redundancy or filler.

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?

Given no output schema and moderate complexity (5 params, 1 nested object), the description is functional but minimal. It effectively differentiates from siblings but does not cover the full update surface (e.g., include parameter is not mentioned) or explain return values. The schema fills some gaps, but for a mutation tool without annotations, the description is not fully contextual.

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 the baseline is 3. The description names a few parameters (stage, disqualification flag, CV) but does not add detail beyond the schema's own descriptions. It provides a helpful high-level mapping but no extra semantic depth, so it neither improves nor detracts from the schema's clarity.

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 clearly states the tool's function: updating application fields like stage, disqualification flag, and CV. It distinguishes itself from sibling tools by explicitly pointing to hires_move_application and hires_advance_application for explicit stage transitions, making its purpose and scope unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: use this for general updates, but prefer specialized siblings for stage transitions. This directly addresses when to use this tool vs alternatives, which is exactly what this dimension requires.

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

Deploy Server

Other Tools