Skip to main content
Glama

TrueInterview

Update an application

update_application
Idempotent

Change one tracked application by its id: move its status (in any direction, because the candidate asked), add a note or set the next interview date. Ask the candidate before moving a status based on something you inferred, such as an email. The answer points at what the new stage leads to: prep for an interview, reviews at an offer.

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": "update_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
statusNo
application_idYes
interview_roundNoThe interview round; alone, it moves the row to that round.
next_interview_dateNoYYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuine behavioral context beyond them — statuses move in both directions and inferred moves need candidate confirmation — but the final sentence about "what the new stage leads to" is vague, and it never says whether an added note replaces or appends to an existing one, which matters for a repeat-safe (idempotent) write.

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?

Three sentences, front-loaded with the core operation and identifier, with the safety rule placed before the optional flavor text. The closing sentence about prep and offer reviews is the weakest line — evocative but imprecise about what the response actually contains.

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?

For a 5-parameter mutation tool with 40% schema coverage and no output schema, the description should close more gaps than it does: interview_round semantics are left to the schema, note append/replace behavior is unstated, and the return value is gestured at rather than described. It is adequate but not complete.

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?

With only 40% schema description coverage, the description must carry more weight: it covers application_id, status, note and next_interview_date at a high level, but omits interview_round entirely and leaves "add a note" ambiguous (append vs overwrite) despite the 1000-character limit. It adds useful meaning for status directionality but does not fully compensate for the coverage gap.

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?

"Change one tracked application by its id" states a specific verb (change) and a scoped resource (one tracked application), then enumerates the three mutation surfaces: status, note, next interview date. This clearly separates it from siblings like update_application_answers, though no sibling is named explicitly.

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 gives real conditions: status may move "in any direction, because the candidate asked," and it explicitly requires asking the candidate before any status move based on an inference like an email. It stops short of naming alternatives (e.g. track_application for creating, update_application_answers for answer edits), so routing is inferred rather than stated.

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