Skip to main content
Glama

TrueInterview

Log an application

track_application
Idempotent

Record a role in the candidate's tracker, for example once they confirm they applied on the employer's site. It records the outcome and sends nothing to the employer. Identify the role by job_id, or by company and role (with job_url if you have it). Safe to repeat: an existing row is updated, and it never moves backwards in the funnel. Call this only after the candidate has told you what happened.

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": {
      "status": "<status>"
    },
    "name": "track_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
roleNo
job_idNo
statusYesWhere the application stands now.
channelNoe.g. "company site", "referral".
companyNo
job_urlNo
applied_atNoYYYY-MM-DD, when status is "applied".
interview_roundNoWith status "interview".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover idempotency and non-destructiveness, yet the description adds real context the annotations don't: nothing is sent to the employer, repeated calls update an existing row, and the funnel never regresses. It doesn't say what a conflicting status does to existing note/interview fields, but the safety profile is well conveyed.

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?

Four short sentences, front-loaded with purpose then trigger then identification then safety guarantees; each carries information. Minor slack in 'for example once they confirm they applied on the employer's site'.

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 9-parameter mutation tool with no output schema, the definition covers identity resolution, idempotency and the no-external-send guarantee. It omits what the call returns and how optional fields like note, channel, applied_at and interview_round interact with the recorded row, so an agent still has gaps.

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?

At 44% schema coverage the description must compensate, and it does add the key identity-resolution logic: job_id, or company plus role, optionally job_url. However, it says nothing about status (the only required param), note, channel, applied_at, or interview_round, leaving the majority of the parameters to a sparse schema.

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 ('Record a role in the candidate's tracker') plus the triggering event (candidate confirms they applied). It does not explicitly distinguish itself from the sibling update_application, which also mutates tracked rows, so an agent must infer the split from the 'safe to repeat / never moves backwards' sentence.

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?

Gives a concrete when-to-use trigger and a hard precondition ('Call this only after the candidate has told you what happened'), which is unusually explicit guidance. It stops short of naming alternatives (update_application, report_application) or stating when-not to use it.

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