Skip to main content
Glama

TrueInterview

Start the setup the candidate handed you

claim_setup_handoff

Start or continue the TrueInterview setup the candidate handed you. With the one-time handoff code they pasted (it starts with tih_): redeem it; the code works once, within five minutes of being copied, and only for the account this connection belongs to. Without a code, when the candidate asks to continue their TrueInterview setup: pick up the setup this account left open in an earlier session. Either way returns the setup instructions to follow in order, with a run_code for report_setup_progress; each call issues a new run_code and the earlier one stops working. Keep the code and the run code out of what you write back to the candidate.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "claim_setup_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the constraints that actually govern behavior: the code is single-use, valid only within five minutes of copying, and bound to this connection's account. It also explains that each call mints a new run_code and invalidates the prior one, which is critical non-obvious state behavior.

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?

It is front-loaded with purpose, then branches into the two usage paths, then discloses return value and secret-handling. Dense but every clause carries operational weight; the semicolon-chained sentence about redemption is slightly hard to parse but not wasteful.

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

Completeness5/5

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

For a stateful, non-idempotent tool with no output schema, the description covers what is returned ('setup instructions to follow in order, with a run_code') and the security handling of both secrets. An agent has everything needed to call it correctly and act on the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden, and it does: it establishes the code is optional, gives its prefix format ('tih_'), and states the one-time and five-minute lifetime plus account binding. That is far more meaning than the bare 'string, 1-100 chars' schema conveys.

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 opens with a specific verb and resource: 'Start or continue the TrueInterview setup the candidate handed you.' It splits the tool into its two distinct modes (redeem a handoff code vs. resume an open setup), so an agent knows exactly what operation this is and how it differs from the follow-up sibling report_setup_progress.

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?

It gives explicit routing: with a code starting 'tih_', redeem it; without a code, use this 'when the candidate asks to continue their TrueInterview setup.' It also names the downstream tool (report_setup_progress) the returned run_code is for, so both entry and continuation are unambiguous.

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