Skip to main content
Glama

AIML Rounds

Mock interview

mock_interview
Read-only

Mock interview rounds per role, with model answers and what the interviewer listens for. No round: list the role's rounds. Keep include_answers false while the learner is answering; set it true to give feedback.

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": {
      "role": "<role>"
    },
    "name": "mock_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes'ai-engineering', 'ml-engineering' or 'data-science'
roundNoRound id or name
include_answersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description explains that the tool can either list rounds or return model answers and interviewer expectations. It does not describe response structure or formatting, but the key behavioral modes are disclosed.

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

Conciseness5/5

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

The description is compact and front-loaded: purpose first, then listing behavior, then the include_answers guidance. Every sentence provides actionable information without wasted wording.

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

Completeness4/5

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

For a read-only tool with no output schema, the description adequately covers what the tool returns and how to control answer visibility. A little more detail about output shape would help, but the core context needed to invoke it is present.

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?

The schema covers 67% of parameters, and the description adds meaningful semantics for round omission and include_answers usage. It clarifies the practical effect of not supplying a round and when to enable answers, going beyond the raw schema text.

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?

The description clearly identifies the resource and value: mock interview rounds per role, including model answers and interviewer focus points. It does not explicitly differentiate itself from siblings like quiz or get_lesson, so it falls short of a 5.

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 concrete usage guidance for the round and include_answers parameters: omit round to list available rounds, and toggle include_answers depending on whether the learner is answering or receiving feedback. It does not mention when to prefer this tool over sibling tools, but its operational guidance is clear.

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