Skip to main content
Glama

TrueInterview

Get the steps for a task

get_playbook
Read-onlyIdempotent

The step-by-step working rules for one kind of task, written for an AI agent: what to call in which order, what to ask the candidate, and the lines never to cross. Read it once at the start of the task and follow it; it replaces installing the TrueInterview skills. task: overview (rules for every task), kickoff (first session), find_jobs, check_fit, resume, apply (answering one application form, which the candidate fills in and sends), tracker, inbox (recruiter email), prep (one company’s interviews) or reach_out. Free, read-only, the same for everyone.

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": {
      "task": "<task>"
    },
    "name": "get_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhich task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds meaningful context by explaining that the content is free, read-only, the same for everyone, and written for an AI agent. It does not cover rate limits or output format, but for a simple read-only resource the added transparency is solid.

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?

The description is dense but front-loads the core definition and usage instruction before listing the task types. Every sentence contributes, though the single long paragraph and inline enum list could be easier to scan if slightly structured. It is appropriately sized for the amount of information conveyed.

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 simple read-only retrieval tool with one enum parameter, the description covers what it returns, when to use it, and what each task category means in enough cases. The annotations and 100% schema coverage handle the rest, and no output schema means return-format explanation is unnecessary.

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

Parameters4/5

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

Schema coverage is 100%, so the enum is already documented as 'Which task.' The description goes beyond the schema by mapping several enum values to their meaning, such as overview for rules for every task, kickoff for the first session, apply for answering one application form, inbox for recruiter email, and prep for one company's interviews. Some values like find_jobs, check_fit, resume, tracker, and reach_out are left to their self-explanatory names, but the added context is valuable.

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 states a specific verb and resource: it returns step-by-step working rules for one kind of task, written for an AI agent, with details on call order, candidate questions, and boundaries. It distinguishes itself by saying it replaces installing the TrueInterview skills and by enumerating the task types it covers. An agent can tell this is a rules-retrieval tool rather than an action tool.

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 clear timing guidance: 'Read it once at the start of the task and follow it.' It also implies that this is the replacement for installing TrueInterview skills. It does not explicitly state when not to use it or name a sibling alternative, but the usage context is strong.

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