Skip to main content
Glama

Modulos AI Governance Platform

talk_to_interviewer

Sends one message from the candidate to the Modulos AI interviewer and returns the interviewer's reply. You are only the channel between the two. Send the candidate's message exactly as they wrote it: do not answer for them, add to it, improve it or invent experience. Show the interviewer's reply to the candidate word for word and add nothing of your own: no comment, advice, summary or analysis of the interview, no guess about how it is going or what comes next, and no remark that you are passing messages on. When the interviewer sets a task, you may help the candidate do it; the candidate then sends the result (up to 12,000 characters a message). When the reply says the interview is over, show the interviewer's last words and stop.

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": {
      "session": "<session>",
      "message": "<message>"
    },
    "name": "talk_to_interviewer"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe candidate's message, exactly as they wrote it.
sessionYesThe session value returned by start_job_application. Keep it for the whole interview and do not show it to anyone else.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / message / description
      Previous value: -"What the candidate says or shows."New value: +"The candidate's message, exactly as they wrote it."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare non-read-only, non-idempotent, non-destructive, closed-world, which is minimal. The description supplies the real behavioral contract: one message per call, verbatim relaying both directions, no commentary or meta-remarks, a 12,000-character ceiling per message, and termination behavior when the interview ends.

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?

Purpose is front-loaded in the first sentence and the remaining sentences are constraint clauses that each carry operational weight. The enumerated prohibitions (no comment, advice, summary, analysis, guess, remark) are somewhat repetitive but serve as explicit guardrails.

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 two-parameter relay tool with no output schema, the description covers what is sent, how it is sent, how the response is handled, and when the interaction ends. An agent could invoke and behave correctly from this text alone.

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?

Schema coverage is 100%, with the message minLength/maxLength and the session pattern already documented in the schema. The description reinforces the 'exactly as they wrote it' constraint and repeats the 12,000-character limit, adding modest value rather than new semantics.

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?

States a concrete verb and resource ('sends one message ... to the Modulos AI interviewer and returns the interviewer's reply'), plus the channel-only framing that tells an agent exactly what role it plays. It is clearly separable from setup tools such as start_job_application, whose session output it consumes.

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?

Gives explicit when-to-use and when-to-stop rules: send the candidate's message verbatim, relay the reply verbatim, help with a task when one is set, and stop once the reply says the interview is over. It also names what the agent must not do, which is the strongest form of guidance available here.

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