Skip to main content
Glama

atlas_interview_followup

A probing follow-up question to a candidate's answer to an interview question (1 credit). Answers directly.

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": {
      "context_id": "<context_id>",
      "candidate_id": "<candidate_id>",
      "original_question": "<original_question>",
      "candidate_answer": "<candidate_answer>"
    },
    "name": "atlas_interview_followup"
  }
}

Input Schema

NameRequiredDescriptionDefault
context_idYesFrom atlas_list_contexts
candidate_idYesFrom atlas_list_candidates
pressure_levelNostandard
candidate_answerYes
original_questionYesE.g. from atlas_generate_interview

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / candidate_answer / description
      Removed value: -"The candidate's answer to the original question"
    • changedInput schema / properties / candidate_id / description
      Previous value: -"Candidate ID from atlas_upload_candidate or atlas_list_candidates"New value: +"From atlas_list_candidates"
    • changedInput schema / properties / context_id / description
      Previous value: -"Context ID from atlas_create_context or atlas_list_contexts"New value: +"From atlas_list_contexts"
    • changedInput schema / properties / original_question / description
      Previous value: -"The original question from atlas_generate_interview output"New value: +"E.g. from atlas_generate_interview"
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the description does not need to repeat safety basics. It adds only '(1 credit)' and the unclear phrase 'Answers directly'; it does not explain state changes, persistence, latency, or what the generated follow-up looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is very short and front-loaded, with no wasted sentences. However, its brevity crosses into under-specification, and the phrase 'Answers directly' is not clear enough to earn full conciseness credit.

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

Completeness2/5

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

For a tool with five parameters, four required, no output schema, and open-world/non-idempotent behavior, the description is far too incomplete. It omits required ID semantics, pressure_level meaning, usage boundaries, and return expectations.

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

Parameters2/5

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

Schema description coverage is 60%, so the schema documents some parameters, but the description provides no parameter guidance and does not explain the required context_id, candidate_id, pressure_level enum, or the expected format for original_question/candidate_answer.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a follow-up question tied to a candidate's answer to an interview question, so the general purpose is inferable. However, it is a noun phrase rather than a clear verb+resource, and 'Answers directly' is ambiguous, leaving the exact action less precise than a strong definition would provide.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as atlas_generate_interview. Usage is only implied by the word 'follow-up' in the name and description.

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